From: Jeff Garzik <jgarzik@pobox.com>
To: hadi@cyberus.ca
Cc: Patrick McHardy <kaber@trash.net>,
"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>,
Stephen Hemminger <shemminger@linux-foundation.org>,
netdev@vger.kernel.org, cramerj <cramerj@intel.com>,
"Kok, Auke-jan H" <auke-jan.h.kok@intel.com>,
"Leech, Christopher" <christopher.leech@intel.com>,
davem@davemloft.net
Subject: Re: [PATCH] IPROUTE: Modify tc for new PRIO multiqueue behavior
Date: Fri, 27 Apr 2007 11:43:47 -0400 [thread overview]
Message-ID: <46321A33.8050103@pobox.com> (raw)
In-Reply-To: <1177685918.4059.67.camel@localhost>
jamal wrote:
> Heres the way i see it from a user perspective:
> If a NIC has 3 hardware queues; if that NIC supports strict priority
> (i.e the prio qdisc) which we already support, there should be no need
> for the user to really explicitly enable that support.
> It should be transparent to them - because by configuring a multi queue
> prio qdisc (3 bands/queues default), they are already doing multiqueues.
Agreed.
Jeff
next prev parent reply other threads:[~2007-04-27 15:44 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 1:39 [PATCH] IPROUTE: Modify tc for new PRIO multiqueue behavior Peter P Waskiewicz Jr
2007-04-25 4:05 ` Stephen Hemminger
2007-04-25 11:36 ` jamal
2007-04-25 17:45 ` Waskiewicz Jr, Peter P
2007-04-26 13:27 ` jamal
2007-04-26 15:57 ` Patrick McHardy
2007-04-26 16:30 ` Waskiewicz Jr, Peter P
2007-04-26 16:44 ` Patrick McHardy
2007-04-26 16:50 ` Waskiewicz Jr, Peter P
2007-04-27 15:09 ` jamal
2007-04-27 15:45 ` Waskiewicz Jr, Peter P
2007-04-30 12:56 ` jamal
2007-05-01 18:27 ` Waskiewicz Jr, Peter P
2007-05-01 22:11 ` jamal
2007-05-01 23:04 ` Waskiewicz Jr, Peter P
2007-05-02 12:43 ` jamal
2007-05-03 21:03 ` Waskiewicz Jr, Peter P
2007-05-03 23:54 ` jamal
2007-05-04 15:48 ` Waskiewicz Jr, Peter P
2007-05-04 20:01 ` Stephen Hemminger
2007-05-04 20:06 ` David Miller
2007-05-04 20:43 ` Waskiewicz Jr, Peter P
2007-05-04 21:00 ` David Miller
2007-05-04 21:22 ` Johannes Berg
2007-05-08 9:33 ` Zhu Yi
2007-05-08 9:45 ` Johannes Berg
2007-05-08 13:28 ` jamal
2007-05-08 15:35 ` Waskiewicz Jr, Peter P
2007-05-08 23:28 ` jamal
2007-05-10 3:02 ` Zhu Yi
2007-05-10 12:35 ` jamal
2007-05-11 1:58 ` Zhu Yi
2007-05-11 2:23 ` jamal
2007-05-10 18:22 ` Waskiewicz Jr, Peter P
2007-05-10 20:00 ` jamal
2007-05-09 14:16 ` Johannes Berg
2007-04-27 14:58 ` jamal
2007-04-27 15:43 ` Jeff Garzik [this message]
2007-04-27 15:46 ` Waskiewicz Jr, Peter P
2007-04-26 18:49 ` Jan Engelhardt
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=46321A33.8050103@pobox.com \
--to=jgarzik@pobox.com \
--cc=auke-jan.h.kok@intel.com \
--cc=christopher.leech@intel.com \
--cc=cramerj@intel.com \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=shemminger@linux-foundation.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.