[Top] [All Lists]

Re: [RFC] netif_rx: receive path optimization

To: Rick Jones <rick.jones2@xxxxxx>
Subject: Re: [RFC] netif_rx: receive path optimization
From: Nivedita Singhvi <niv@xxxxxxxxxx>
Date: Thu, 31 Mar 2005 16:30:25 -0800
Cc: netdev <netdev@xxxxxxxxxxx>
In-reply-to: <424C8790.6060203@xxxxxx>
References: <20050330132815.605c17d0@xxxxxxxxxxxxxxxxx> <20050331120410.7effa94d@xxxxxxxxxxxxxxxxx> <1112303431.1073.67.camel@xxxxxxxxxxxxxxxx> <424C6A98.1070509@xxxxxx> <1112305084.1073.94.camel@xxxxxxxxxxxxxxxx> <424C7CDC.8050801@xxxxxx> <424C81B8.6090709@xxxxxxxxxx> <424C8790.6060203@xxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217
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 :).


<Prev in Thread] Current Thread [Next in Thread>