Herman wrote:
Its only the MTU 1500 case with non-TSO that we are
discussing here so copying a few bytes is really not a big
deal as the data is already in cache from copying into
kernel. If it lets the adapter run at speed, thats what
customers want and what we need. Granted, if the HW could
deal with this we would not have to, but thats not the case
today so I want to spend a few CPU cycles to get best
performance. Again, if this is not done on other platforms, I
don't understand why you care.
I care because adding the arch-specific hack creates a maintenance issue
for me.
-scott
On Mon, 2003-06-16 at 11:21, Feldman, Scott wrote:
Herman wrote:
quoted
Its only the MTU 1500 case with non-TSO that we are
discussing here so copying a few bytes is really not a big
deal as the data is already in cache from copying into
kernel. If it lets the adapter run at speed, thats what
customers want and what we need. Granted, if the HW could
deal with this we would not have to, but thats not the case
today so I want to spend a few CPU cycles to get best
performance. Again, if this is not done on other platforms, I
don't understand why you care.
I care because adding the arch-specific hack creates a maintenance issue
for
Scott, would you be pleased if something was implemented out of the
driver, in generic net code? Something that all the drivers could use,
even if nothing but e1000 used it for now.
--
Dave Hansen
haveblue@us.ibm.com