From: Nivedita Singhvi <niv@us.ibm.com>
To: Rick Jones <rick.jones2@hp.com>
Cc: netdev <netdev@oss.sgi.com>
Subject: Re: [RFC] netif_rx: receive path optimization
Date: Thu, 31 Mar 2005 16:30:25 -0800 [thread overview]
Message-ID: <424C9621.70606@us.ibm.com> (raw)
In-Reply-To: <424C8790.6060203@hp.com>
Rick Jones wrote:
> Well, I'm in an email discussion with someone who seems to bump their
> TCP windows quite large, and disable timestamps...
Ah, an oldie but a goodie :), disabling route inheritance
as a result, bumping up their default rto back to 300ms, just
so many things that could go wrong there...
> BTW what is the real world purpose of having the multiple CPU affinity
> of NIC interrupts? I have to admit it seems rather alien to me. (In
> the context of no onboard NIC smarts being involved that is)
Featuritis Bloatis ;). It's a marketing requirement :).
thanks,
Nivedita
next prev parent reply other threads:[~2005-04-01 0:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-30 21:28 [PATCH] netif_rx: receive path optimization Stephen Hemminger
2005-03-30 21:57 ` jamal
2005-03-30 22:08 ` jamal
2005-03-30 23:53 ` Stephen Hemminger
2005-03-31 3:16 ` jamal
2005-03-31 20:04 ` [RFC] " Stephen Hemminger
2005-03-31 21:10 ` Jamal Hadi Salim
2005-03-31 21:17 ` Stephen Hemminger
2005-03-31 21:25 ` Jamal Hadi Salim
2005-03-31 21:43 ` Eric Lemoine
2005-03-31 22:02 ` Stephen Hemminger
2005-03-31 21:24 ` Rick Jones
2005-03-31 21:38 ` jamal
2005-03-31 22:42 ` Rick Jones
2005-03-31 23:03 ` Nivedita Singhvi
2005-03-31 23:28 ` Rick Jones
2005-04-01 0:10 ` Stephen Hemminger
2005-04-01 0:42 ` Rick Jones
2005-04-01 0:30 ` Nivedita Singhvi [this message]
2005-03-31 23:36 ` jamal
2005-04-01 0:07 ` Rick Jones
2005-04-01 1:17 ` jamal
2005-04-01 18:22 ` Rick Jones
2005-04-01 16:40 ` Andi Kleen
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=424C9621.70606@us.ibm.com \
--to=niv@us.ibm.com \
--cc=netdev@oss.sgi.com \
--cc=rick.jones2@hp.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).