From: "Holger Hoffstaette" <holger@wizards.de>
To: linux-kernel@vger.kernel.org
Cc: netdev@vger.kernel.org
Subject: Re: Reproducible data corruption with sendfile+vsftp - splice regression?
Date: Sat, 15 Dec 2007 14:43:18 +0100 [thread overview]
Message-ID: <pan.2007.12.15.13.43.18.232625@wizards.de> (raw)
In-Reply-To: 20071206184426.GA32599@electric-eye.fr.zoreil.com
On Thu, 06 Dec 2007 19:44:26 +0100, Francois Romieu wrote:
> Holger Hoffstaette <holger@wizards.de> : [...]
>> Maybe turning off sendfile or NAPI just lead to random success - so far
>> it really looks like tso on the r8169 is the common cause.
>
> TSO on the r8169 is the magic switch but the regression makes imvho more
> sense from a VM pov:
>
> - the corrupted file has the same size as the expected file
> - the corrupted file exhibits holes which come as a multiple of 4096 bytes
> (8*4k, 2 places, there may be more)
> - the r8169 driver does not know what a page is
> - the 8169 hardware has a small 8192 bytes Tx buffer
>
> It would be nice if someone could do a sendfile + vsftp test with TSO on a
> different hardware. While I could not reproduce the corruption when simply
> downloading a file that I had copied on the server with scp, it triggered
> almost immediately after I copied it locally and tried to download the
> copy.
I tested 2.6.24-rc5 on my T60 (Intel e1000 built with NAPI) and installed
vsftp/apache with sendfile and enabled all offload options incl. TSO.
Repeated downloads of >500 MB with ftp or wget over the NIC onto ram- or
physical disk gives no corruption whatsoever. Speed of download to ramdisk
is a nice continuous 125 MB/sec.
Looks like the r8169 or the driver after all..
thanks
Holger
prev parent reply other threads:[~2007-12-15 13:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <pan.2007.11.29.23.42.52.661624@wizards.de>
2007-11-30 8:07 ` Reproducible data corruption with sendfile+vsftp - splice regression? Eric Dumazet
2007-11-30 9:20 ` Holger Hoffstaette
2007-11-30 10:39 ` Holger Hoffstaette
2007-11-30 18:26 ` Rick Jones
2007-12-02 16:00 ` Holger Hoffstaette
2007-12-02 20:49 ` Holger Hoffstaette
2007-12-05 22:54 ` Francois Romieu
2007-12-06 1:13 ` Francois Romieu
2007-12-06 9:41 ` Holger Hoffstaette
2007-12-06 9:28 ` Holger Hoffstaette
2007-12-06 18:44 ` Francois Romieu
2007-12-08 15:28 ` Mark Lord
2007-12-13 2:19 ` Holger Hoffstaette
2007-12-15 10:24 ` Holger Hoffstaette
2007-12-15 13:43 ` Holger Hoffstaette [this message]
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=pan.2007.12.15.13.43.18.232625@wizards.de \
--to=holger@wizards.de \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).