From: Andi Kleen <ak@suse.de>
To: Ben Mansell <ben@zeus.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: TCP push missing with writev()
Date: Thu, 30 Nov 2000 19:14:14 +0100 [thread overview]
Message-ID: <20001130191414.A13814@gruyere.muc.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.30.0011301710020.8071-100000@artemis.cam.zeus.com>
In-Reply-To: <Pine.LNX.4.30.0011301710020.8071-100000@artemis.cam.zeus.com>; from ben@zeus.com on Thu, Nov 30, 2000 at 05:35:41PM +0000
On Thu, Nov 30, 2000 at 05:35:41PM +0000, Ben Mansell wrote:
> (possibly treading on ground covered before:
> http://www.uwsg.iu.edu/hypermail/linux/kernel/9904.1/0304.html )
>
> To be brief and to the point: Should there be any difference between the
> following two ways of writing data to a TCP socket?
>
> 1) write( fd, buffer, length )
> 2) writev( fd, {buffer, length}, {NULL,0} )
No.
>
> The problem is that if data happens to be written via method (2), then
> the PUSH flag is never set on any packets generated. This is a bug,
> surely?
I just tried it on 2.2.17 and 2.4.0test11 and it sets PUSH for writev()
for both cases just fine. Maybe you could supply a test program and tcpdump
logs for what you think is wrong ?
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-30 18:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-30 17:35 Ben Mansell
2000-11-30 18:14 ` Andi Kleen [this message]
2000-11-30 18:54 ` Ben Mansell
2000-11-30 20:15 ` David S. Miller
2000-11-30 22:57 ` Ben Mansell
2000-11-30 23:01 ` David S. Miller
2000-12-01 0:15 ` Ben Mansell
2000-12-01 0:08 ` David S. Miller
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=20001130191414.A13814@gruyere.muc.suse.de \
--to=ak@suse.de \
--cc=ben@zeus.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®