From: Olaf Kirch <okir@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] 2.6 UDP recvmsg vs POSIX
Date: Tue, 24 Feb 2004 10:32:34 +0100 [thread overview]
Message-ID: <20040224093234.GB7886@suse.de> (raw)
In-Reply-To: <20040223094216.66602afd.davem@redhat.com>
On Mon, Feb 23, 2004 at 09:42:16AM -0800, David S. Miller wrote:
> Therefore, the only bug was returning -EAGAIN unconditionally and that's
> what is fixed by the correct half of your changes.
>
> TCP does the same thing Olaf, and there is no way I'm adding the gross poll
> hacks there :-)
Okay, I can live with that. I will push this info to our posix
guys and let them chew on it.
UDPv6 needs the exact same fix BTW.
Cheers,
Olaf
--
Olaf Kirch | Stop wasting entropy - start using predictable
okir@suse.de | tempfile names today!
---------------+
prev parent reply other threads:[~2004-02-24 9:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 12:17 [PATCH] 2.6 UDP recvmsg vs POSIX Olaf Kirch
2004-02-18 4:30 ` Andi Kleen
2004-02-18 6:17 ` David S. Miller
2004-02-19 7:07 ` Andi Kleen
2004-02-21 21:08 ` David S. Miller
2004-02-23 9:42 ` Olaf Kirch
2004-02-23 17:42 ` David S. Miller
2004-02-24 9:32 ` Olaf Kirch [this message]
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=20040224093234.GB7886@suse.de \
--to=okir@suse.de \
--cc=davem@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).