From: jamal <hadi@cyberus.ca>
To: Donald Becker <becker@scyld.com>
Cc: "Feldman, Scott" <scott.feldman@intel.com>,
Jeff Garzik <jgarzik@pobox.com>,
netdev@oss.sgi.com, ricardoz@us.ibm.com
Subject: RE: [e1000 2.6 10/11] TxDescriptors -> 1024 default
Date: 15 Sep 2003 07:37:45 -0400 [thread overview]
Message-ID: <1063625865.1077.56.camel@jzny.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0309121003430.1442-100000@beotest.scyld.com>
On Fri, 2003-09-12 at 11:29, Donald Becker wrote:
> Remember the purpose of the driver (hardware) Tx queue.
> It should be the minimum size consistent with
> Keeping the wire busy(1) when we have queued packets
> Cache locality(2) when queueing Tx packets
> Allowing interrupt mitigation
> It is *not* supposed to act as an additional buffer in the system.
> Unlike the queue layer, it cannot be changed dynamically, classify
> packets, re-order based on priority or do any of the future clever
> improvements possible with the general-purpose, device-independent
> software queue.
>
> (1) A short gap with atypical traffic is entirely acceptable
>
> (2) Cache locality isn't important because we need local performance. It's
> important to minimize cache line displacement for the rest of the
> system, especially the application.
Dont know how much time you have, but this would be a good paper if you
wrote one. Since you already have gathered data "in the days when CPUs
were slow", you can complement it with newer data. If you dont have
time, i am sure there are people who will be interested in collecting
data for you.
cheers,
jamal
next prev parent reply other threads:[~2003-09-15 11:37 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 5:13 [e1000 2.6 10/11] TxDescriptors -> 1024 default Feldman, Scott
2003-09-12 12:44 ` jamal
2003-09-12 15:29 ` Donald Becker
2003-09-12 17:44 ` Ricardo C Gonzalez
2003-09-15 11:37 ` jamal [this message]
2003-09-12 18:12 ` Ben Greear
2003-09-12 18:31 ` Ricardo C Gonzalez
2003-09-15 11:29 ` jamal
[not found] <Pine.LNX.4.58.0405141430340.4622@fcat>
2004-05-18 14:34 ` Ricardo C Gonzalez
2004-06-02 19:11 ` Marc Herbert
[not found] <3F60DE5B.1010700@pobox.com>
2003-09-11 21:27 ` Ricardo C Gonzalez
-- strict thread matches above, loose matches on Subject: below --
2003-09-09 3:14 Feldman, Scott
2003-09-11 19:18 ` Jeff Garzik
2003-09-11 19:45 ` Ben Greear
2003-09-11 19:59 ` Jeff Garzik
2003-09-11 20:12 ` David S. Miller
2003-09-11 20:40 ` Ben Greear
2003-09-11 21:07 ` David S. Miller
2003-09-11 21:29 ` Ben Greear
2003-09-11 21:29 ` David S. Miller
2003-09-11 21:47 ` Ricardo C Gonzalez
2003-09-11 22:00 ` Jeff Garzik
2003-09-11 22:15 ` Ben Greear
2003-09-11 23:02 ` David S. Miller
2003-09-11 23:22 ` Ben Greear
2003-09-11 23:29 ` David S. Miller
2003-09-12 1:34 ` jamal
2003-09-12 2:20 ` Ricardo C Gonzalez
2003-09-12 3:05 ` jamal
2003-09-13 3:49 ` David S. Miller
2003-09-13 11:52 ` Robert Olsson
2003-09-15 12:12 ` jamal
2003-09-15 13:45 ` Robert Olsson
2003-09-15 23:15 ` David S. Miller
2003-09-16 9:28 ` Robert Olsson
2003-09-14 19:08 ` Ricardo C Gonzalez
2003-09-15 2:50 ` David Brownell
2003-09-15 8:17 ` David S. 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=1063625865.1077.56.camel@jzny.localdomain \
--to=hadi@cyberus.ca \
--cc=becker@scyld.com \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=ricardoz@us.ibm.com \
--cc=scott.feldman@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