Reply-To: <hzhong@cisco.com>
From: "Hua Zhong" <hzhong@cisco.com>
To: "'David S. Miller'" <davem@davemloft.net>,
       "'Martijn Sipkema'" <msipkema@sipkema-digital.com>
Cc: <cfriesen@nortelnetworks.com>, <jst1@email.com>,
       <linux-kernel@vger.kernel.org>, <alan@lxorguk.ukuu.org.uk>,
       <davem@redhat.com>
Subject: RE: UDP recvmsg blocks after select(), 2.6 bug?
Date: Thu, 7 Oct 2004 15:46:23 -0700
Organization: Cisco Systems
Message-ID: <012001c4acbf$786766f0$b83147ab@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <20041007152400.17e8f475.davem@davemloft.net>
Importance: Normal
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1090
Lines: 27

> I can't believe this thread has lasted this long.

The reason is that you haven't just admitted very clearly that 
"Linux select isn't Posix compliant and it was a design decision 
not to do so for performance reasons". I think this kind of 
authorative answer would shut up many people. :-)

> I think people had cotton in their ears when I mentioned 
> that every single 2.4.x and 2.6.x existing system out there 
> has this behavior, therefore even if we changed the behavior 
> some way today people still need to handle this to work on 
> all existing Linux systems.

Unfortunately this isn't the best argument..

I think most people just hope Linux would follow the standard.
The old Linux threads weren't posix-compliant either for years,
and people still fixed (most of?) it in 2.6. By your argument
that would not have happened.

Hua

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/