From: Roland Dreier <rdreier@cisco.com>
To: hadi@cyberus.ca
Cc: Patrick McHardy <kaber@trash.net>,
David Miller <davem@davemloft.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: Fri, 18 Jul 2008 10:10:21 -0700 [thread overview]
Message-ID: <adaljzz6ruq.fsf@cisco.com> (raw)
In-Reply-To: <1216386624.4833.94.camel@localhost> (jamal's message of "Fri, 18 Jul 2008 09:10:24 -0400")
> The question is whether the packets sitting on the fifo qdisc are being
> sorted fairly when congestion kicks in. Remember there is still a single
> wire still even on multiple rings;->
This is definitely true, but it is good to keep in mind that in the near
future we will start to see things look a little like multiple "virtual
wires." This is because of new ethernet standards like per-priority
pause, which makes it possible that one hardware ring on a NIC can
transmit while another ring is paused (possibly because of congestion
far off in the network).
- R.
next prev parent reply other threads:[~2008-07-18 17:10 UTC|newest]
Thread overview: 58+ 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 13:03 ` Patrick McHardy
2008-07-17 13:12 ` David Miller
2008-07-17 13:48 ` Patrick McHardy
2008-07-17 22:36 ` David Miller
2008-07-17 23:58 ` Patrick McHardy
2008-07-17 13:35 ` jamal
2008-07-17 14:02 ` Patrick McHardy
2008-07-17 22:24 ` David Miller
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-20 15:16 ` jamal
2008-07-20 17:25 ` David Miller
2008-07-20 17:34 ` Tomas Winkler
2008-07-20 17:35 ` David Miller
2008-07-20 22:32 ` jamal
2008-07-20 23:59 ` David Miller
2008-07-21 2: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 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:22 ` Herbert Xu
2008-07-21 15:26 ` David Miller
2008-07-21 16:16 ` Herbert Xu
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:08 ` David Miller
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 10:42 ` David Miller
2008-08-22 10:47 ` Herbert Xu
2008-08-22 13:52 ` jamal
2008-08-22 13:43 ` jamal
2008-07-21 17:35 ` David Miller
2008-07-18 17:10 ` Roland Dreier [this message]
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 15:35 ` jamal
2008-07-21 0:11 ` Herbert Xu
2008-07-21 2:33 ` jamal
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-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=adaljzz6ruq.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).