From: Andrew Morton <akpm@linux-foundation.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Stephen Hemminger <shemminger@vyatta.com>,
David Miller <davem@davemloft.net>,
pstaszewski@itcare.pl, netdev@vger.kernel.org
Subject: Re: [PATCH] dst: call cond_resched() in dst_gc_task()
Date: Mon, 8 Feb 2010 23:31:15 -0800 [thread overview]
Message-ID: <20100208233115.456d847c.akpm@linux-foundation.org> (raw)
In-Reply-To: <1265700036.4236.120.camel@edumazet-laptop>
On Tue, 09 Feb 2010 08:20:36 +0100 Eric Dumazet <eric.dumazet@gmail.com> wrote:
> I suppose offlining a cpu migrates its works to another (online) cpu ?
Sort of, effectively. The workqueue code runs all the pending works on
the to-be-offlined CPU and then it's done.
schedule_delayed_work() starts out with a timer, and the timer code
_does_ perform migration off the going-away CPU.
next prev parent reply other threads:[~2010-02-09 7:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-08 13:16 Problem wit route cache Paweł Staszewski
2010-02-08 13:28 ` Eric Dumazet
2010-02-08 13:33 ` Paweł Staszewski
2010-02-08 13:51 ` Eric Dumazet
2010-02-08 13:59 ` Paweł Staszewski
2010-02-08 14:06 ` Eric Dumazet
2010-02-08 14:16 ` Paweł Staszewski
2010-02-08 14:32 ` Eric Dumazet
2010-02-08 19:32 ` [PATCH] dst: call cond_resched() in dst_gc_task() Eric Dumazet
2010-02-08 23:01 ` David Miller
2010-02-09 6:07 ` Eric Dumazet
2010-02-08 23:26 ` Andrew Morton
2010-02-08 23:34 ` David Miller
2010-02-08 23:37 ` Andrew Morton
2010-02-08 23:50 ` David Miller
2010-02-08 23:50 ` Stephen Hemminger
2010-02-09 6:06 ` Eric Dumazet
2010-02-09 6:35 ` Andrew Morton
2010-02-09 7:20 ` Eric Dumazet
2010-02-09 7:31 ` Andrew Morton [this message]
2010-02-08 14:32 ` Problem wit route cache Paweł Staszewski
2010-02-08 14:45 ` Paweł Staszewski
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=20100208233115.456d847c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pstaszewski@itcare.pl \
--cc=shemminger@vyatta.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 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.