From: "David S. Miller" <davem@redhat.com>
To: "Robert White" <rwhite@casabyte.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tcp_push_pending_frames() without TCP_CORK or TCP_NODELAY
Date: Fri, 30 Jul 2004 15:37:00 -0700 [thread overview]
Message-ID: <20040730153700.2bb46976.davem@redhat.com> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA2ZSI4XW+fk25FhAf9BqjtMKAAAAQAAAAto7TSbyGCEOKEjP4Tiu9VgEAAAAA@casabyte.com>
On Fri, 30 Jul 2004 15:02:33 -0700
"Robert White" <rwhite@casabyte.com> wrote:
> 4) Cork-then-uncork would still end up with two syscalls instead of one.
Syscalls are incredible cheap, this is not an argument for not
using cork'ing.
next prev parent reply other threads:[~2004-07-30 22:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 2:19 tcp_push_pending_frames() without TCP_CORK or TCP_NODELAY Robert White
2004-07-30 2:36 ` David S. Miller
2004-07-30 22:02 ` Robert White
2004-07-30 22:37 ` David S. Miller [this message]
2004-07-31 8:10 ` Arjan van de Ven
2004-08-02 2:54 ` David S. Miller
2004-08-02 19:44 ` Robert White
2004-08-02 19:53 ` Arjan van de Ven
2004-08-02 20:18 ` Robert White
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=20040730153700.2bb46976.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rwhite@casabyte.com \
/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