netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. K. Cliburn" <jcliburn@gmail.com>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: netdev@vger.kernel.org, ian@jeffray.co.uk
Subject: Re: sendfile() behavior while troubleshooting netdevice
Date: Tue, 29 Jul 2008 08:32:34 -0500	[thread overview]
Message-ID: <488F1BF2.8090009@bellsouth.net> (raw)
In-Reply-To: <20080729062804.GA7009@2ka.mipt.ru>

Evgeniy Polyakov wrote:
> Hi Jay.
> 
> On Mon, Jul 28, 2008 at 07:07:07PM -0500, Jay Cliburn (jacliburn@bellsouth.net) wrote:
>> sendfile() + TSO + atl1 driver == corrupted file at the receiver
> 
> ...
> 
>> The hosts:
>> server, petrel,  r8169, 192.168.1.6,   2.6.20-1.2320.fc5
>> client, sparrow, e100,  192.168.1.195, 2.6.25.6-27.fc8
> 
> ...
> 
>> [jcliburn@sparrow ~]$ ./sfcli 192.168.1.6 testfile
>> connected...
>> file size is 1600 bytes
>> received 1592 bytes
>> error: expected 1600, received 1592
> 
> I.e. trouble also happens with r8169 driver?
> 

I think you may be right, Evgeniy.  I thought I had tested things using 
e100 as the server side, but apparently I didn't.  If I run the server 
from the e100 host, it works flawlessly every time.  (But of course, the 
NIC doesn't support TSO, either.)

More testing tonight...

Thanks.

  reply	other threads:[~2008-07-29 13:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-29  0:07 sendfile() behavior while troubleshooting netdevice Jay Cliburn
2008-07-29  0:27 ` Ian Jeffray
2008-07-29  0:52   ` Jay Cliburn
2008-07-29  6:28 ` Evgeniy Polyakov
2008-07-29 13:32   ` J. K. Cliburn [this message]
2008-07-29  9:32 ` Jarek Poplawski
2008-07-29 13:16   ` J. K. Cliburn

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=488F1BF2.8090009@bellsouth.net \
    --to=jcliburn@gmail.com \
    --cc=ian@jeffray.co.uk \
    --cc=jacliburn@bellsouth.net \
    --cc=johnpol@2ka.mipt.ru \
    --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).