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:21:38 -0700 (PDT) [thread overview]
Message-ID: <20080619.022138.265296442.davem@davemloft.net> (raw)
In-Reply-To: <OF38F6814F.441FEEF8-ON6525746D.0032B3BA-6525746D.00331325@in.ibm.com>
From: Krishna Kumar2 <krkumar2@in.ibm.com>
Date: Thu, 19 Jun 2008 14:47:52 +0530
> What about core networking changes? I think you were planning to
> remove a lot of stuff (device busy checks, requeue's, etc?) and
> also implement lockless code (sch_generic.c at the very least).
> Are those ready for taking an initial look?
We can't do that completely until every driver has it's TX path
converted, which isn't likely to happen so we'll have a compat
layer for a long time.
I haven't touched one line of generic code yet. It isn't necessary
to test out all of these ideas.
next prev parent reply other threads:[~2008-06-19 9:21 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
2008-06-19 9:17 ` Krishna Kumar2
2008-06-19 9:21 ` David Miller [this message]
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.022138.265296442.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