From: David Miller <davem@davemloft.net>
To: okir@lst.de
Cc: netdev@vger.kernel.org
Subject: Re: Races in net_rx_action vs netpoll?
Date: Tue, 10 Jul 2007 22:44:57 -0700 (PDT) [thread overview]
Message-ID: <20070710.224457.95896396.davem@davemloft.net> (raw)
In-Reply-To: <200707101244.32753.okir@lst.de>
From: Olaf Kirch <okir@lst.de>
Date: Tue, 10 Jul 2007 12:44:31 +0200
> On Tuesday 10 July 2007 00:27, David Miller wrote:
> > I'm happy to entertain this kind of solution, but we really
> > need to first have an interface to change multiple bits
> > at a time in one atomic operation, because by itself this
> > patch doubles the number of atomices we do when starting
> > a NAPI poll.
>
> Understood. How about the patch below? It takes a similar
> approach, but it puts the onus on the netpoll code
> path rather than the general NAPI case.
Definitely looks more palatable.
> @@ -919,6 +921,14 @@ static inline void netif_rx_complete(str
> {
> unsigned long flags;
>
> +#ifdef CONFIG_NETPOLL
> + /* Prevent race with netpoll - yes, this is a kludge.
> + * But at least it doesn't penalize the non-netpoll
> + * code path. */
> + if (test_bit(__LINK_STATE_POLL_LIST_FROZEN, &dev->state))
> + return;
> +#endif
> +
> local_irq_save(flags);
> BUG_ON(!test_bit(__LINK_STATE_RX_SCHED, &dev->state));
> list_del(&dev->poll_list);
That new bit can be set in interrupt context can't it?
next prev parent reply other threads:[~2007-07-11 5:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 12:16 Races in net_rx_action vs netpoll? Olaf Kirch
2007-07-09 22:27 ` David Miller
2007-07-10 10:44 ` Olaf Kirch
2007-07-11 5:44 ` David Miller [this message]
2007-07-11 7:41 ` Olaf Kirch
2007-07-12 2:33 ` David Miller
2007-07-19 15:19 ` Olaf Kirch
2007-07-19 16:27 ` Stephen Hemminger
2007-07-22 7:05 ` David Miller
2007-07-24 10:26 ` Jarek Poplawski
2007-07-12 12:59 ` Jarek Poplawski
2007-07-12 13:54 ` Olaf Kirch
2007-07-13 8:55 ` Jarek Poplawski
2007-07-16 8:06 ` Jarek Poplawski
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=20070710.224457.95896396.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=okir@lst.de \
/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.