From: Iker <iker@computer.org>
To: linux-kernel@vger.kernel.org
Subject: self piping and context switching
Date: Fri, 12 Sep 2003 21:19:20 -0400 [thread overview]
Message-ID: <039401c37995$0f30cbd0$3203a8c0@duke> (raw)
Assume a thread is monitoring a set of fd's which include both ends of
a pipe (using poll, for example). If the thread writes to the pipe (in
order to notify itself for whatever reason) is it reasonable to expect
that it will be able to return to its poll loop and get the event
without a context switch? (provided it quickly returns to the poll
loop).
Regards,
Iker
next reply other threads:[~2003-09-13 1:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 1:19 Iker [this message]
2003-09-13 2:04 ` David Schwartz
2003-09-13 2:56 ` [lkml] " Iker
2003-09-13 3:31 ` David Schwartz
2003-09-13 17:10 ` Alan Cox
2003-09-13 19:37 ` Jamie Lokier
2003-09-15 23:36 ` Robert White
[not found] <20030916194101.GA29266@mail.jlokier.co.uk>
[not found] ` <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA2ZSI4XW+fk25FhAf9BqjtMKAAAAQAAAAXdCgZz9uCkifnVjI6hutcwEAAAAA@casabyte.com>
[not found] ` <20030916213826.GA29814@mail.jlokier.co.uk>
2003-09-16 21:41 ` Jamie Lokier
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='039401c37995$0f30cbd0$3203a8c0@duke' \
--to=iker@computer.org \
--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
all inboxes | Powered by JetHome®