From: David Miller <davem@davemloft.net>
To: jarkao2@gmail.com
Cc: netdev@vger.kernel.org, vinay@linux.vnet.ibm.com,
krkumar2@in.ibm.com, mchan@broadcom.com, Matheos.Worku@Sun.COM,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 11/39]: netdev: Move next_sched into struct netdev_queue.
Date: Mon, 14 Jul 2008 05:00:11 -0700 (PDT) [thread overview]
Message-ID: <20080714.050011.186100773.davem@davemloft.net> (raw)
In-Reply-To: <20080714114913.GA4504@ff.dom.local>
From: Jarek Poplawski <jarkao2@gmail.com>
Date: Mon, 14 Jul 2008 11:49:13 +0000
> On 03-07-2008 09:03, David Miller wrote:
> > We schedule queues, not the device, for output queue
> > processing in BH.
> >
> ...
> > diff --git a/net/core/dev.c b/net/core/dev.c
> > index 8e38948..c5e3532 100644
> > --- a/net/core/dev.c
> > +++ b/net/core/dev.c
> > @@ -1323,13 +1323,14 @@ static void dev_queue_xmit_nit(struct sk_buff *skb, struct net_device *dev)
> > void __netif_schedule(struct net_device *dev)
> > {
> > if (!test_and_set_bit(__LINK_STATE_SCHED, &dev->state)) {
>
> Isn't this bit supposed to be set/tested per queue as well, or do I
> miss something?
That shoule not happen until my later patches which switch that all
over.
See patch 5/13 which I posted on Thursday, Jul 10. That's when the
transition from "global queue state + per-queue state" into "only
per-queue state" happens.
Until that point, we have to keep the existing quasi-multi-queue
semantics in order to not break drivers etc.
next prev parent reply other threads:[~2008-07-14 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 7:03 [PATCH 11/39]: netdev: Move next_sched into struct netdev_queue David Miller
2008-07-14 11:49 ` Jarek Poplawski
2008-07-14 12:00 ` David Miller [this message]
2008-07-14 12:27 ` 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=20080714.050011.186100773.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Matheos.Worku@Sun.COM \
--cc=jarkao2@gmail.com \
--cc=krkumar2@in.ibm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=vinay@linux.vnet.ibm.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