From: David Miller <davem@davemloft.net>
To: krkumar2@in.ibm.com
Cc: netdev@vger.kernel.org
Subject: Re: Multiple TX queue implementation and Batching
Date: Thu, 19 Jun 2008 02:10:39 -0700 (PDT) [thread overview]
Message-ID: <20080619.021039.193704469.davem@davemloft.net> (raw)
In-Reply-To: <OF50454112.AA19F7EA-ON6525746D.002A115D-6525746D.002AD61A@in.ibm.com>
From: Krishna Kumar2 <krkumar2@in.ibm.com>
Date: Thu, 19 Jun 2008 13:17:53 +0530
> Would it be possible to get a sneak preview of your multiple tx queue
> implementation (along with a complete re-write of the entire tx path)?
>
> I would like to see if batching would make sense with the new design,
> or becomes redundant (or something to be done entirely at the drivers).
Right now I'm just hacking drivers in preparation for this, so
that the transmit queueing is seperated from the location
in the driver where this actually occurs.
I'll post a set of tg3 driver patches once I'm done debugging
things.
next prev parent reply other threads:[~2008-06-19 9:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 7:47 Multiple TX queue implementation and Batching Krishna Kumar2
2008-06-19 9:10 ` David Miller [this message]
2008-06-19 9:17 ` Krishna Kumar2
2008-06-19 9:21 ` David Miller
2008-06-19 9:22 ` 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=20080619.021039.193704469.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=krkumar2@in.ibm.com \
--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