diff options
author | Rusty Russell <rusty@rustcorp.com.au> | 2011-12-28 19:43:15 -0500 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2011-12-29 16:44:29 -0500 |
commit | f1776dade17cd54562f4bc1d01de89c4908b4dd0 (patch) | |
tree | f598aa5a7e2c9922a0031b0ced571d92fcca1f62 /mm/mempolicy.c | |
parent | b2baed69e605c3e57d28940cc7aaae908d61f769 (diff) |
virtio_net: use non-reentrant workqueue.
Michael S. Tsirkin also noticed that we could run the refill work
multiple CPUs: if we kick off a refill on one CPU and then on another,
they would both manipulate the queue at the same time (they use
napi_disable to avoid racing against the receive handler itself).
Tejun points out that this is what the WQ_NON_REENTRANT flag is for,
and that there is a convenient system kthread we can use.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'mm/mempolicy.c')
0 files changed, 0 insertions, 0 deletions