From: Rick Jones <rick.jones2@hp.com>
To: netdev@oss.sgi.com
Subject: Re: is UDP_CORK "real"
Date: Thu, 21 Apr 2005 16:53:44 -0700 [thread overview]
Message-ID: <42683D08.7030201@hp.com> (raw)
In-Reply-To: <20050421162505.3db8ed7c.davem@davemloft.net>
David S. Miller wrote:
> On Thu, 21 Apr 2005 16:14:56 -0700
> Rick Jones <rick.jones2@hp.com> wrote:
>
>
>>Is UDP_CORK going to be an ongoing feature?
>
>
> Yes, it's there and it's real.
>
> If netperf is passing a TCP socket option number in for
> a setsockopt() on a UDP socket, how in the world is that
> the kernel's problem?
I didn't really mean to say that it was a kernel problem per se. I was trying to
understand the space, make sure that it was deliberate that there were actual
overlaps between the TCP_mumble and UDP_mumble options and such. The release
bits for netperf 2.4.0 will have checks to make sure it does not try to set
"TCP_NODLEAY" on a UDP socket. Call it a 13 year lingering misfeature in
netperf if you like :)
rick jones
next prev parent reply other threads:[~2005-04-21 23:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 23:14 is UDP_CORK "real" Rick Jones
2005-04-21 23:25 ` David S. Miller
2005-04-21 23:53 ` Rick Jones [this message]
2005-04-26 13:40 ` Andi Kleen
2005-04-27 8:20 ` Michael Kerrisk
[not found] ` <426F2A1D.10001@aarnet.edu.au>
2005-04-27 12:26 ` network manpages was " Andi Kleen
2005-04-27 18:43 ` David S. Miller
2005-04-29 15:29 ` Andi Kleen
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=42683D08.7030201@hp.com \
--to=rick.jones2@hp.com \
--cc=netdev@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.