From: "David S. Miller" <davem@redhat.com>
To: ak@suse.de
Cc: ben@zeus.com, linux-kernel@vger.kernel.org
Subject: Re: TCP push missing with writev()
Date: Thu, 30 Nov 2000 12:15:57 -0800 [thread overview]
Message-ID: <200011302015.MAA06647@pizda.ninka.net> (raw)
In-Reply-To: <20001130191414.A13814@gruyere.muc.suse.de> (message from Andi Kleen on Thu, 30 Nov 2000 19:14:14 +0100)
In-Reply-To: <Pine.LNX.4.30.0011301710020.8071-100000@artemis.cam.zeus.com> <20001130191414.A13814@gruyere.muc.suse.de>
Date: Thu, 30 Nov 2000 19:14:14 +0100
From: Andi Kleen <ak@suse.de>
> 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 ?
One thing which could affect the behavior is if the Zeus
folks are futzing around with the TCP_CORK socket option.
Ben, are you guys playing with it?
Finally, are you doing these writes from a userspace program
or directly inside of a kernel module?
Later,
David S. Miller
davem@redhat.com
-
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 21:02 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
2000-11-30 18:54 ` Ben Mansell
2000-11-30 20:15 ` David S. Miller [this message]
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=200011302015.MAA06647@pizda.ninka.net \
--to=davem@redhat.com \
--cc=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®