Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp289561imu; Thu, 8 Nov 2018 19:59:31 -0800 (PST) X-Google-Smtp-Source: AJdET5fhKxburHO2aq9ZlftulAKTqBGow0+Z9rHsU2WluCDa8sE+KzR+00ZrE7RcWTkLjOCA1tqS X-Received: by 2002:a17:902:2006:: with SMTP id n6-v6mr7401582pla.131.1541735971371; Thu, 08 Nov 2018 19:59:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541735971; cv=none; d=google.com; s=arc-20160816; b=djx9mKn3qr7Zl9D5fJAl3NCeeThhV8EdCBoD4GfHIz8AHm7gfiD83RVjCqXV+qCOyo Ukoot0NsTUUBZa37pVEPP8ZFuBpaf/MELdptpSPncuI6ySfIP1H4jvVBvAaoXNlIapia 7jiFIktFXNyrkxnIlVkoszCGqC7Z8IurFTsGrijFn7cCg615/7cTfDj5RZ3MUpT2NdJO 2F/4ulYKbqWn3TWVJiTO4p6HglAA8EcVVvBqmfYcIBMYwWH7mQnAV8L8Xt2Bi6Hr0L8L xAAxUdpAt4jXwBhEw9AHCTl2teowmA0YdkDxCFS9vzM9CwH3d4ETR3A0IY9zSV4ngShK JD+g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=XglSBdJIg+/+57+qzItBE5F+W8JwZ5Pefl3hAkb70Us=; b=gMNBX80mSRTi9+W3+eGVJDLnXqpFagpudGuXJzd8ObYQRhiPHhentMg52yNRmXT83M C8r7h/ySoN2l7NigS4ctkyU6HC8/GhdvYOB139YXigahcbm94J1WrMZ42IPBmH3SWYTk RdgVNCboxG4PcpE+in5s7GxGoRikZmSZEZe7PkwX+LhU3yfXcwvy/lF74VjRXPjwlwYm UXJukKBj7ygcDKFW3iA7kkk06DrhLLtamco/9dIfFhJpl3McWf3i/jPvrK/jq2YhnucF wM6vnDMsnpY3SelsO3sXfy7cLAIVCm4AsCPy7kMv54/pBy0g96hCoLWRepgUobWovDjU D97g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x68-v6si6345669pfc.0.2018.11.08.19.59.16; Thu, 08 Nov 2018 19:59:31 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727825AbeKINhb (ORCPT + 99 others); Fri, 9 Nov 2018 08:37:31 -0500 Received: from mx1.redhat.com ([209.132.183.28]:39598 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727238AbeKINhb (ORCPT ); Fri, 9 Nov 2018 08:37:31 -0500 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 07B2DC0C05A5; Fri, 9 Nov 2018 03:58:49 +0000 (UTC) Received: from redhat.com (ovpn-120-200.rdu2.redhat.com [10.10.120.200]) by smtp.corp.redhat.com (Postfix) with ESMTP id C0FFE5D78D; Fri, 9 Nov 2018 03:58:44 +0000 (UTC) Date: Thu, 8 Nov 2018 22:58:44 -0500 From: "Michael S. Tsirkin" To: Jason Wang Cc: Tiwei Bie , virtualization@lists.linux-foundation.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, virtio-dev@lists.oasis-open.org, wexu@redhat.com, jfreimann@redhat.com Subject: Re: [PATCH net-next v2 3/5] virtio_ring: add packed ring support Message-ID: <20181108225555-mutt-send-email-mst@kernel.org> References: <20180711022711.7090-1-tiwei.bie@intel.com> <20180711022711.7090-4-tiwei.bie@intel.com> <20181107123933-mutt-send-email-mst@kernel.org> <20181108013759.GA20591@debian> <2d46a41e-bc00-276a-e19a-105c9dffc75a@redhat.com> <20181108091337-mutt-send-email-mst@kernel.org> <21d6dbd9-8f78-6939-0e80-27b470aeb00a@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <21d6dbd9-8f78-6939-0e80-27b470aeb00a@redhat.com> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.32]); Fri, 09 Nov 2018 03:58:49 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 09, 2018 at 10:25:28AM +0800, Jason Wang wrote: > > On 2018/11/8 下午10:14, Michael S. Tsirkin wrote: > > On Thu, Nov 08, 2018 at 04:18:25PM +0800, Jason Wang wrote: > > > On 2018/11/8 上午9:38, Tiwei Bie wrote: > > > > > > + > > > > > > + if (vq->vq.num_free < descs_used) { > > > > > > + pr_debug("Can't add buf len %i - avail = %i\n", > > > > > > + descs_used, vq->vq.num_free); > > > > > > + /* FIXME: for historical reasons, we force a notify here if > > > > > > + * there are outgoing parts to the buffer. Presumably the > > > > > > + * host should service the ring ASAP. */ > > > > > I don't think we have a reason to do this for packed ring. > > > > > No historical baggage there, right? > > > > Based on the original commit log, it seems that the notify here > > > > is just an "optimization". But I don't quite understand what does > > > > the "the heuristics which KVM uses" refer to. If it's safe to drop > > > > this in packed ring, I'd like to do it. > > > > > > According to the commit log, it seems like a workaround of lguest networking > > > backend. I agree to drop it, we should not have such burden. > > > > > > But we should notice that, with this removed, the compare between packed vs > > > split is kind of unfair. > > I don't think this ever triggers to be frank. When would it? > > > I think it can happen e.g in the path of XDP transmission in > __virtnet_xdp_xmit_one(): > > >         err = virtqueue_add_outbuf(sq->vq, sq->sg, 1, xdpf, GFP_ATOMIC); >         if (unlikely(err)) >                 return -ENOSPC; /* Caller handle free/refcnt */ > I see. We used to do it for regular xmit but stopped doing it. Is it fine for xdp then? > > > > > Consider the removal of lguest support recently, > > > maybe we can drop this for split ring as well? > > > > > > Thanks > > If it's helpful, then for sure we can drop it for virtio 1. > > Can you see any perf differences at all? With which device? > > > I don't test but consider the case of XDP_TX in guest plus vhost_net in > host. Since vhost_net is half duplex, it's pretty easier to trigger this > condition. > > Thanks Sounds reasonable. Worth testing before we change things though. > > > > > > > commit 44653eae1407f79dff6f52fcf594ae84cb165ec4 > > > > Author: Rusty Russell > > > > Date: Fri Jul 25 12:06:04 2008 -0500 > > > > > > > > virtio: don't always force a notification when ring is full > > > > We force notification when the ring is full, even if the host has > > > > indicated it doesn't want to know. This seemed like a good idea at > > > > the time: if we fill the transmit ring, we should tell the host > > > > immediately. > > > > Unfortunately this logic also applies to the receiving ring, which is > > > > refilled constantly. We should introduce real notification thesholds > > > > to replace this logic. Meanwhile, removing the logic altogether breaks > > > > the heuristics which KVM uses, so we use a hack: only notify if there are > > > > outgoing parts of the new buffer. > > > > Here are the number of exits with lguest's crappy network implementation: > > > > Before: > > > > network xmit 7859051 recv 236420 > > > > After: > > > > network xmit 7858610 recv 118136 > > > > Signed-off-by: Rusty Russell > > > > > > > > diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c > > > > index 72bf8bc09014..21d9a62767af 100644 > > > > --- a/drivers/virtio/virtio_ring.c > > > > +++ b/drivers/virtio/virtio_ring.c > > > > @@ -87,8 +87,11 @@ static int vring_add_buf(struct virtqueue *_vq, > > > > if (vq->num_free < out + in) { > > > > pr_debug("Can't add buf len %i - avail = %i\n", > > > > out + in, vq->num_free); > > > > - /* We notify*even if* VRING_USED_F_NO_NOTIFY is set here. */ > > > > - vq->notify(&vq->vq); > > > > + /* FIXME: for historical reasons, we force a notify here if > > > > + * there are outgoing parts to the buffer. Presumably the > > > > + * host should service the ring ASAP. */ > > > > + if (out) > > > > + vq->notify(&vq->vq); > > > > END_USE(vq); > > > > return -ENOSPC; > > > > } > > > > > > > >