From: "Michael S. Tsirkin" <mst@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Herbert Xu <herbert@gondor.hengli.com.au>,
netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
virtualization@lists.linux-foundation.org,
Ken Stailey <kstailey@yahoo.com>
Subject: Re: [PATCH] virtio_net: Add schedule check to napi_enable call
Date: Thu, 10 Feb 2011 19:57:26 +0200 [thread overview]
Message-ID: <20110210175725.GA9674@redhat.com> (raw)
In-Reply-To: <201102101232.50526.rusty@rustcorp.com.au>
On Thu, Feb 10, 2011 at 12:32:50PM +1030, Rusty Russell wrote:
> From: "Bruce Rogers" <brogers@novell.com>
>
> Under harsh testing conditions, including low memory, the guest would
> stop receiving packets. With this patch applied we no longer see any
> problems in the driver while performing these tests for extended periods
> of time.
>
> Make sure napi is scheduled subsequent to each napi_enable.
>
> Signed-off-by: Bruce Rogers <brogers@novell.com>
> Signed-off-by: Olaf Kirch <okir@suse.de>
> Cc: stable@kernel.org
> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Rusty, so this is 2.6.38 material - you'll send this to Linus? Or DaveM?
> ---
> drivers/net/virtio_net.c | 27 ++++++++++++++++-----------
> 1 file changed, 16 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
> --- a/drivers/net/virtio_net.c
> +++ b/drivers/net/virtio_net.c
> @@ -446,6 +446,20 @@ static void skb_recv_done(struct virtque
> }
> }
>
> +static void virtnet_napi_enable(struct virtnet_info *vi)
> +{
> + napi_enable(&vi->napi);
> +
> + /* If all buffers were filled by other side before we napi_enabled, we
> + * won't get another interrupt, so process any outstanding packets
> + * now. virtnet_poll wants re-enable the queue, so we disable here.
> + * We synchronize against interrupts via NAPI_STATE_SCHED */
> + if (napi_schedule_prep(&vi->napi)) {
> + virtqueue_disable_cb(vi->rvq);
> + __napi_schedule(&vi->napi);
> + }
> +}
> +
> static void refill_work(struct work_struct *work)
> {
> struct virtnet_info *vi;
> @@ -454,7 +468,7 @@ static void refill_work(struct work_stru
> vi = container_of(work, struct virtnet_info, refill.work);
> napi_disable(&vi->napi);
> still_empty = !try_fill_recv(vi, GFP_KERNEL);
> - napi_enable(&vi->napi);
> + virtnet_napi_enable(vi);
>
> /* In theory, this can happen: if we don't get any buffers in
> * we will *never* try to fill again. */
> @@ -638,16 +652,7 @@ static int virtnet_open(struct net_devic
> {
> struct virtnet_info *vi = netdev_priv(dev);
>
> - napi_enable(&vi->napi);
> -
> - /* If all buffers were filled by other side before we napi_enabled, we
> - * won't get another interrupt, so process any outstanding packets
> - * now. virtnet_poll wants re-enable the queue, so we disable here.
> - * We synchronize against interrupts via NAPI_STATE_SCHED */
> - if (napi_schedule_prep(&vi->napi)) {
> - virtqueue_disable_cb(vi->rvq);
> - __napi_schedule(&vi->napi);
> - }
> + virtnet_napi_enable(vi);
> return 0;
> }
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-10 17:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 2:02 [PATCH] virtio_net: Add schedule check to napi_enable call Rusty Russell
2011-02-10 17:57 ` Michael S. Tsirkin
2011-02-10 17:57 ` Michael S. Tsirkin [this message]
2011-02-10 19:01 ` David Miller
2011-02-10 19:01 ` David Miller
2011-02-10 19:03 ` David Miller
2011-02-10 19:03 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2011-02-10 2:02 Rusty Russell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110210175725.GA9674@redhat.com \
--to=mst@redhat.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.hengli.com.au \
--cc=kstailey@yahoo.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.