mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Riesen <Alexander.Riesen@synopsys.com>
To: erc@pobox.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is the linux networking code broken?
Date: Fri, 31 May 2002 10:45:59 +0200	[thread overview]
Message-ID: <20020531104559.A23756@riesen-pc.gr05.synopsys.com> (raw)
In-Reply-To: <20020531064959.GD1402@riesen-pc.gr05.synopsys.com> <20020531024623.K4707-101000@ranger.pns.bellsouth.net>

On Fri, May 31, 2002 at 02:47:21AM -0500, Ed Carp wrote:
> On Fri, 31 May 2002, Alex Riesen wrote:
> 
> > Neither of them. How do you think the things are working here? 8-)
> > rsync, wget, apache, a whole lot other programs transfer megabytes.
> 
> Most of them use short writes.  Here's the source I'm using...

Most of them are the biggest possible writes.

~/compile/ercftp ./sender localhost ../nfs-kaboom.c
Using 2048 byte packets
Connecting to localhost
Resolved, opening TCP socket
Doing connect
Connected, waiting for OK...
Waiting for OK...
Sending ../nfs-kaboom.c
... a while
Waiting for ack...
caught signal 14!


~/compile/ercftp ./receiver 
Getting TCP socket
Doing bind
Doing listen
Accepting connection
Writing 23987 to ../nfs-kaboom.c
... another while

caught signal 14! flen=23987, inlen=0, pos=0, packets=12, packet.seqno=0


Neither of the programs finished because of awful lot of bugs within,
but the output clearly shows the facts.
Surely, no problems with networking observed.

What kernel do you use? Also, you may want check your system libraries
(libc, libresolv*).

-alex

       reply	other threads:[~2002-05-31  8:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020531064959.GD1402@riesen-pc.gr05.synopsys.com>
     [not found] ` <20020531024623.K4707-101000@ranger.pns.bellsouth.net>
2002-05-31  8:45   ` Alex Riesen [this message]
2002-05-31  0:12 Ed Carp

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=20020531104559.A23756@riesen-pc.gr05.synopsys.com \
    --to=alexander.riesen@synopsys.com \
    --cc=erc@pobox.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®