From: Rusty Russell <rusty@rustcorp.com.au>
To: Avi Kivity <avi@redhat.com>
Cc: Pierre Ossman <drzeus-list@drzeus.cx>,
Minchan Kim <minchan.kim@gmail.com>,
kvm@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Wu Fengguang <fengguang.wu@intel.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Rik van Riel <riel@redhat.com>,
netdev@vger.kernel.org
Subject: Re: Page allocation failures in guest
Date: Wed, 12 Aug 2009 16:26:30 +0930 [thread overview]
Message-ID: <200908121626.31531.rusty@rustcorp.com.au> (raw)
In-Reply-To: <4A825601.60000@redhat.com>
On Wed, 12 Aug 2009 03:11:21 pm Avi Kivity wrote:
> > + /* In theory, this can happen: if we don't get any buffers in
> > + * we will*never* try to fill again. Sleeping in keventd if
> > + * bad, but that is worse. */
> > + if (still_empty) {
> > + msleep(100);
> > + schedule_work(&vi->refill);
> > + }
> > +}
> > +
>
> schedule_delayed_work()?
Hmm, might as well, although this is v. unlikely to happen.
Thanks,
Rusty.
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
@@ -72,7 +72,7 @@ struct virtnet_info
struct sk_buff_head send;
/* Work struct for refilling if we run low on memory. */
- struct work_struct refill;
+ struct delayed_work refill;
/* Chain pages by the private ptr. */
struct page *pages;
@@ -402,19 +402,16 @@ static void refill_work(struct work_stru
struct virtnet_info *vi;
bool still_empty;
- vi = container_of(work, struct virtnet_info, refill);
+ vi = container_of(work, struct virtnet_info, refill.work);
napi_disable(&vi->napi);
try_fill_recv(vi, GFP_KERNEL);
still_empty = (vi->num == 0);
napi_enable(&vi->napi);
/* In theory, this can happen: if we don't get any buffers in
- * we will *never* try to fill again. Sleeping in keventd if
- * bad, but that is worse. */
- if (still_empty) {
- msleep(100);
- schedule_work(&vi->refill);
- }
+ * we will *never* try to fill again. */
+ if (still_empty)
+ schedule_delayed_work(&vi->refill, HZ/2);
}
static int virtnet_poll(struct napi_struct *napi, int budget)
@@ -434,7 +431,7 @@ again:
if (vi->num < vi->max / 2) {
if (!try_fill_recv(vi, GFP_ATOMIC))
- schedule_work(&vi->refill);
+ schedule_delayed_work(&vi->refill, 0);
}
/* Out of packets? */
@@ -925,7 +922,7 @@ static int virtnet_probe(struct virtio_d
vi->vdev = vdev;
vdev->priv = vi;
vi->pages = NULL;
- INIT_WORK(&vi->refill, refill_work);
+ INIT_DELAYED_WORK(&vi->refill, refill_work);
/* If they give us a callback when all buffers are done, we don't need
* the timer. */
@@ -991,7 +988,7 @@ static int virtnet_probe(struct virtio_d
unregister:
unregister_netdev(dev);
- cancel_work_sync(&vi->refill);
+ cancel_delayed_work_sync(&vi->refill);
free_vqs:
vdev->config->del_vqs(vdev);
free:
@@ -1020,7 +1017,7 @@ static void virtnet_remove(struct virtio
BUG_ON(vi->num != 0);
unregister_netdev(vi->dev);
- cancel_work_sync(&vi->refill);
+ cancel_delayed_work_sync(&vi->refill);
vdev->config->del_vqs(vi->vdev);
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-08-12 6:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 9:51 Pierre Ossman
2009-07-13 14:59 ` Minchan Kim
2009-08-11 6:32 ` Pierre Ossman
2009-08-11 6:52 ` Avi Kivity
2009-08-12 3:19 ` Rusty Russell
2009-08-12 5:31 ` Rusty Russell
2009-08-12 5:41 ` Avi Kivity
2009-08-12 6:56 ` Rusty Russell [this message]
2009-08-13 20:25 ` Pierre Ossman
2009-08-26 2:17 ` Rusty Russell
2009-08-26 4:55 ` Pierre Ossman
2009-08-26 12:18 ` Rusty Russell
2009-08-26 19:22 ` David Miller
2009-08-12 6:19 ` Pierre Ossman
2009-08-12 7:43 ` Avi Kivity
2009-08-12 8:22 ` Pierre Ossman
2009-08-12 8:35 ` Avi Kivity
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=200908121626.31531.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=avi@redhat.com \
--cc=drzeus-list@drzeus.cx \
--cc=fengguang.wu@intel.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=riel@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox