From: Vladislav Bolkhovitin <vst@vlnb.net>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Francois Romieu <romieu@fr.zoreil.com>
Subject: r8169 & TX offload
Date: Tue, 16 Oct 2007 19:23:49 +0400 [thread overview]
Message-ID: <4714D785.3000402@vlnb.net> (raw)
Hello,
I've recently bought Realtek RTL8169S-32 chip based Gigabit Ethernet card:
# lspci -vv
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit
Ethernet (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit
Ethernet
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (8000ns min, 16000ns max), Cache Line Size 20
Interrupt: pin A routed to IRQ 10
Region 0: I/O ports at c400 [size=256]
Region 1: Memory at fe9fec00 (32-bit, non-prefetchable) [size=256]
Expansion ROM at fe9c0000 [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
PME(D0-,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
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?
Why they are not enabled by default as it was done for e1000 or tg3? Are
there any hidden drawbacks in enabling them?
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.
Regards,
Vlad
next reply other threads:[~2007-10-16 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 15:23 Vladislav Bolkhovitin [this message]
2007-10-16 17:25 ` r8169 & TX offload Francois Romieu
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=4714D785.3000402@vlnb.net \
--to=vst@vlnb.net \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@fr.zoreil.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