From: Francois Romieu <romieu@fr.zoreil.com>
To: jason.morgan@aveillant.com
Cc: netdev@vger.kernel.org, hayeswang@realtek.com
Subject: Re: tx checksum offload in rtl8168evl disabled in driver
Date: Fri, 4 Oct 2013 01:01:20 +0200 [thread overview]
Message-ID: <20131003230120.GA25047@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <OF3E5567E2.6AC62D58-ON80257BF9.004ED219-80257BF9.004F713D@aveillant.com>
jason.morgan@aveillant.com <jason.morgan@aveillant.com> :
[...]
> I'm at 517Mbps and I've found that there seems to be a cpu bottleneck.
Which kernel ?
> 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 ?
YMMV.
Hayes may elaborate.
--
Ueimor
next prev parent reply other threads:[~2013-10-03 23:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 14:27 tx checksum offload in rtl8168evl disabled in driver jason.morgan
2013-10-03 23:01 ` Francois Romieu [this message]
2013-10-04 3:10 ` hayeswang
2013-10-04 9:37 ` jason.morgan
2013-10-04 9:15 ` jason.morgan
2013-10-05 9:22 ` Francois Romieu
2013-10-08 18:44 ` jason.morgan
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=20131003230120.GA25047@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=hayeswang@realtek.com \
--cc=jason.morgan@aveillant.com \
--cc=netdev@vger.kernel.org \
/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