From: jamal <hadi@cyberus.ca>
To: David Miller <davem@davemloft.net>
Cc: kaber@trash.net, netdev@vger.kernel.org,
johannes@sipsolutions.net, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 20/31]: pkt_sched: Perform bulk of qdisc destruction in RCU.
Date: Sun, 20 Jul 2008 22:20:38 -0400 [thread overview]
Message-ID: <1216606839.4847.159.camel@localhost> (raw)
In-Reply-To: <20080720.165911.86437240.davem@davemloft.net>
On Sun, 2008-20-07 at 16:59 -0700, David Miller wrote:
> Every time this topic comes up, you insist on them having to match.
> And I have no idea why.
I dont insist on them matching, just on correctness. i.e if you say you
have RR, then the scheduling needs to meet those requirements not an
estimate - thats all.
> The problem is that the bottleneck is the qdisc itself since all those
> cpus synchonize on it's lock. We can't have a shared qdisc for the
> device and get full parallelization.
>
> That's why we're having one qdisc per TX queue, so that they all don't
> bunch up on the qdisc lock.
That last sentence i have no issues with - it is what i thought wasnt
happening;-> i misunderstood it to be a single fifo shared by all
hardware tx queues from the begining (otherwise i wouldnt be posting).
We are in sync i think, a single pfifo per TX queue is the way to go. I
was suggesting it goes in the driver, but this is cleaner: In the
future, one could could actually replace the pfifo with another qdisc
since the single virtual wire becomes equivalent to a single virtual
netdevice
> Otherwise, there is zero point in all of these TX multiqueue features
> in the hardware if we can't parallelize things fully.
parallelization is achieveable in the ideal case.
cheers,
jamal
next prev parent reply other threads:[~2008-07-21 2:20 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 12:17 [PATCH 20/31]: pkt_sched: Perform bulk of qdisc destruction in RCU David Miller
2008-07-17 12:17 ` David Miller
2008-07-17 13:03 ` Patrick McHardy
2008-07-17 13:03 ` Patrick McHardy
2008-07-17 13:12 ` David Miller
2008-07-17 13:12 ` David Miller
2008-07-17 13:48 ` Patrick McHardy
2008-07-17 22:36 ` David Miller
2008-07-17 22:36 ` David Miller
2008-07-17 23:58 ` Patrick McHardy
2008-07-17 23:58 ` Patrick McHardy
2008-07-17 13:35 ` jamal
2008-07-17 13:35 ` jamal
2008-07-17 14:02 ` Patrick McHardy
2008-07-17 22:24 ` David Miller
2008-07-17 22:24 ` David Miller
2008-07-17 23:48 ` Patrick McHardy
2008-07-17 23:48 ` Patrick McHardy
2008-07-18 13:10 ` jamal
2008-07-18 13:27 ` jamal
2008-07-18 21:05 ` David Miller
2008-07-18 21:05 ` David Miller
2008-07-20 15:16 ` jamal
2008-07-20 17:25 ` David Miller
2008-07-20 17:34 ` Tomas Winkler
2008-07-20 17:34 ` Tomas Winkler
2008-07-20 17:35 ` David Miller
2008-07-20 17:35 ` David Miller
2008-07-20 22:32 ` jamal
2008-07-20 22:32 ` jamal
2008-07-20 23:59 ` David Miller
2008-07-21 2:20 ` jamal [this message]
2008-07-21 11:20 ` jamal
2008-07-21 11:20 ` jamal
2008-07-21 16:45 ` David Miller
2008-07-21 11:58 ` Herbert Xu
2008-07-21 11:58 ` Herbert Xu
2008-07-21 13:08 ` jamal
2008-07-21 13:08 ` jamal
2008-07-21 13:19 ` Herbert Xu
2008-07-21 13:56 ` jamal
2008-07-21 13:58 ` Herbert Xu
2008-07-21 15:09 ` David Miller
2008-07-21 15:09 ` David Miller
2008-07-21 15:22 ` Herbert Xu
2008-07-21 15:22 ` Herbert Xu
2008-07-21 15:26 ` David Miller
2008-07-21 16:16 ` Herbert Xu
2008-07-21 16:16 ` Herbert Xu
2008-07-21 16:25 ` David Miller
2008-07-21 16:25 ` David Miller
2008-07-21 16:43 ` Herbert Xu
2008-07-21 16:51 ` David Miller
2008-07-21 17:02 ` Herbert Xu
2008-07-21 17:02 ` Herbert Xu
2008-07-21 17:08 ` David Miller
2008-07-21 17:08 ` David Miller
2008-07-21 17:11 ` Herbert Xu
2008-07-21 17:11 ` Herbert Xu
2008-08-22 6:56 ` Herbert Xu
2008-08-22 7:16 ` David Miller
2008-08-22 7:41 ` Herbert Xu
2008-08-22 7:41 ` Herbert Xu
2008-08-22 10:42 ` David Miller
2008-08-22 10:42 ` David Miller
2008-08-22 10:47 ` Herbert Xu
2008-08-22 10:47 ` Herbert Xu
2008-08-22 13:52 ` jamal
2008-08-22 13:52 ` jamal
2008-08-22 13:43 ` jamal
2008-08-22 13:43 ` jamal
2008-07-21 17:35 ` David Miller
2008-07-21 17:35 ` David Miller
2008-07-18 17:10 ` Roland Dreier
2008-07-18 17:10 ` Roland Dreier
2008-07-20 14:58 ` jamal
2008-07-20 14:58 ` jamal
2008-07-20 14:32 ` Herbert Xu
2008-07-20 17:20 ` David Miller
2008-07-20 14:20 ` Herbert Xu
2008-07-20 14:20 ` Herbert Xu
2008-07-20 15:35 ` jamal
2008-07-20 15:35 ` jamal
2008-07-21 0:11 ` Herbert Xu
2008-07-21 2:33 ` jamal
2008-07-21 2:33 ` jamal
2008-07-21 3:17 ` Herbert Xu
2008-07-21 3:17 ` Herbert Xu
2008-07-21 11:14 ` jamal
2008-07-21 11:36 ` Herbert Xu
2008-07-21 11:39 ` jamal
2008-07-21 11:39 ` jamal
2008-07-19 3:59 ` David Miller
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=1216606839.4847.159.camel@localhost \
--to=hadi@cyberus.ca \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=kaber@trash.net \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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.