lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <OF682E8083.1CE559C7-ON80257BFA.00349A7B-80257BFA.0034D52E@aveillant.com>
Date:	Fri, 4 Oct 2013 10:37:12 +0100
From:	jason.morgan@...illant.com
To:	netdev@...r.kernel.org
Subject: RE: tx checksum offload in rtl8168evl disabled in driver

It seems TX Early is a miss-feature, surely this is what needs to be 
turned off by default and not the tx-offload.
Yes it reduces latency, but at the expense of a lower overall throughput.



From:   hayeswang <hayeswang@...ltek.com>
To:     'Francois Romieu' <romieu@...zoreil.com>, 
<jason.morgan@...illant.com>, 
Cc:     <netdev@...r.kernel.org>, 'nic_swsd' <nic_swsd@...ltek.com>
Date:   04/10/2013 04:10
Subject:        RE: tx checksum offload in rtl8168evl disabled in driver



Francois Romieu [mailto:romieu@...zoreil.com] 
[...]
> > I'm using 2k to 4k frames with a rtl8168evl.
> > I've found this message
> > http://www.spinics.net/lists/netdev/msg216530.html
> [...]
> > However the message thread, above indicates that this is 
> not a problem and 
> > can be changed to make tx-checksum offload possible.
> > 
> > However we are using a newer chip to the on in the message 
> thread. I've 
> > tried to find other, more recent citations without success.
> > 
> > So, why is it still turned off ?
> 
> It has been disabled since 
> d58d46b5d85139d18eb939aa7279c160bab70484 ("r8169:
> jumbo fixes"). Patch was submitted as a RFC on 2011/07/17 and 
> Hayes was
> explicitely requested to comment on the jumbo part if 
> necessary. Patch was
> submitted for inclusion on 2011/09/22.
> 
> Tx checksumming and jumbo are mutually exclusive in Realtek's 
> driver as well.
> 
> It seems no recent gigabit chipset reliably supports it.
> 
> > What will be the effect of turning it on (changing false to 
> true, in the 
> > driver line) for our chip ?

Since RTL8111E, the chips support a feature which we call "tx early".
For jumbo frame, the hw starts to send a packet before getting the whole 
data.
However, the checksum has to be calculated after the whole data are 
fetched.
Therefore, the jumbo frame and the tx checksum couldn't be enable at the 
same
time, otherwise a packet with incorrect checksum would be sent.

Best Regards,
Hayes



--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ