From: jamal <hadi@cyberus.ca>
To: Zhu Yi <yi.zhu@intel.com>
Cc: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>,
Johannes Berg <johannes@sipsolutions.net>,
Stephen Hemminger <shemminger@linux-foundation.org>,
Patrick McHardy <kaber@trash.net>,
netdev@vger.kernel.org, jgarzik@pobox.com,
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: Thu, 10 May 2007 22:23:35 -0400 [thread overview]
Message-ID: <1178850215.4074.6.camel@localhost> (raw)
In-Reply-To: <1178848682.3045.82.camel@debian.sh.intel.com>
On Fri, 2007-11-05 at 09:58 +0800, Zhu Yi wrote:
>
> Good, we agree on this.
Good start.
> Now let's solve the problem.
>
Lets take it slowly, because i think i wasnt getting anywhere with
Peter. See if you make sense of what i am saying maybe we can make
progress.
> When the low priority ring buffer is full in the hardware, will you
> suppose the driver call netif_stop_queue() or not?
Yes, I will.
With a note: This is precisely what i have been saying all along
in my posting. I explained my reasoning; if you missed the why I think i
should write it up.
So in order to make progress - i am going to not respond to the rest of
the email; tell me if you dont understand me and i will do a write up
hopefully tommorow or over the weekend.
Or tell me you understand me and disagree because of ....
cheers,
jamal
next prev parent reply other threads:[~2007-05-11 2:23 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 [this message]
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
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=1178850215.4074.6.camel@localhost \
--to=hadi@cyberus.ca \
--cc=auke-jan.h.kok@intel.com \
--cc=christopher.leech@intel.com \
--cc=cramerj@intel.com \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=johannes@sipsolutions.net \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=shemminger@linux-foundation.org \
--cc=yi.zhu@intel.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;
as well as URLs for NNTP newsgroup(s).