| To: | netdev@xxxxxxxxxxx |
|---|---|
| Subject: | Re: is UDP_CORK "real" |
| From: | Rick Jones <rick.jones2@xxxxxx> |
| Date: | Thu, 21 Apr 2005 16:53:44 -0700 |
| In-reply-to: | <20050421162505.3db8ed7c.davem@davemloft.net> |
| References: | <426833F0.9010803@hp.com> <20050421162505.3db8ed7c.davem@davemloft.net> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; HP-UX 9000/785; en-US; rv:1.6) Gecko/20040304 |
David S. Miller wrote:
On Thu, 21 Apr 2005 16:14:56 -0700 Rick Jones <rick.jones2@xxxxxx> wrote: 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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [IPSEC]: Kill nested read lock by deleting xfrm_init_tempsel, Herbert Xu |
|---|---|
| Next by Date: | Re: [IPSEC]: Kill nested read lock by deleting xfrm_init_tempsel, Patrick McHardy |
| Previous by Thread: | Re: is UDP_CORK "real", David S. Miller |
| Next by Thread: | Re: is UDP_CORK "real", Andi Kleen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |