From: "David Schwartz" <davids@webmaster.com>
To: "Robert Hancock" <hancockr@shaw.ca>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: RE: Linux poll() <sigh> again
Date: Fri, 12 May 2006 11:49:35 -0700 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKMENMLNAB.davids@webmaster.com> (raw)
In-Reply-To: <44649FAB.4080806@huawei.com>
> > This may be a bug somewhere.. however, once again if you don't
> > want read
> > to block under any circumstances, set your sockets to non-blocking!
> But that's another hack. AFAICS why ppl (mostly) use select/poll wud be
> to know if their send/recv/read/write would go thru rather than getting
> blocked!
It's not another hack. If you don't want to block, you must tell the kernel
that. As for select/poll telling you that a write won't block, it has never
done that. The select/poll functions, just like almost every other system
call, do *not* provide future guarantees.
DS
next prev parent reply other threads:[~2006-05-12 18:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6bkl7-56Y-11@gated-at.bofh.it>
2006-05-12 0:08 ` Robert Hancock
2006-05-12 11:53 ` linux-os (Dick Johnson)
2006-05-12 14:32 ` Robert Hancock
2006-05-12 14:46 ` jimmy
2006-05-12 14:57 ` linux-os (Dick Johnson)
2006-05-12 15:06 ` Eric Dumazet
2006-05-12 15:12 ` Davide Libenzi
2006-05-12 18:49 ` David Schwartz [this message]
2006-05-11 14:25 linux-os (Dick Johnson)
2006-05-11 20:47 ` Nishanth Aravamudan
2006-05-11 21:04 ` linux-os (Dick Johnson)
2006-05-11 21:16 ` Nishanth Aravamudan
2006-05-12 11:42 ` linux-os (Dick Johnson)
2006-05-12 10:37 ` Jan Engelhardt
2006-05-12 5:26 ` David Schwartz
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=MDEHLPKNGKAHNMBLJOLKMENMLNAB.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome