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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4716499E.9040701@vlnb.net>
Date:	Wed, 17 Oct 2007 21:42:54 +0400
From:	Vladislav Bolkhovitin <vst@...b.net>
To:	Francois Romieu <romieu@...zoreil.com>
CC:	netdev@...r.kernel.org
Subject: Re: r8169 & TX offload

Francois Romieu wrote:
> (please remove l-k from the Cc:, this ought to be sent to netdev)

OK. Sorry, for some reason I thought I read in the MAINTAINERS file that 
LKML is the mailing list for r8169 driver.

> Vladislav Bolkhovitin <vst@...b.net> :
> 
>>I've recently bought Realtek RTL8169S-32 chip based Gigabit Ethernet card:
>>
>># lspci -vv
> 
> [...]
> 
>>I've noticed that all TX offload features (tx-checksumming, 
>>scatter-gather and TSO) are disabled by default and should be manually 
>>enabled by ethtool. I wonder, is there any particular reason for that? 
> 
> As far as I can tell, it is mostly a lack of pressure from the users and
> my desire to avoid a change of behavior.
> 
>>Why they are not enabled by default as it was done for e1000 or tg3? Are 
>>there any hidden drawbacks in enabling them?
> 
> None that I know of. I had not noticed a huge difference and people did
> not comment a lot either...

I think, 30% of CPU saving is worth enough to turn TX offload on, 
especially if a system does something more than just data transfers. 
Usually, such options are enabled by default unless there are some 
hidden important drawbacks, like stability issues. Hence, there are 
questions like mine: it's just too suspicious that something good 
doesn't have hidden issues if it isn't enabled by author ;)

Thanks for clarification.

>>Those offload options are definitely work. They give in my setup (32-bit 
>>66MHz PCI, Xeon 1.7GHz CPU, open-iscsi) CPU offload from 75% to 45% and 
>>data write throughput improvement from 55MB/s to 59MB/s.
> 
> ...but your datapoint is welcome.
> 

-
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