From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Iker <iker@computer.org>
Cc: David Schwartz <davids@webmaster.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [lkml] RE: self piping and context switching
Date: Sat, 13 Sep 2003 18:10:06 +0100 [thread overview]
Message-ID: <1063473005.8519.7.camel@dhcp23.swansea.linux.org.uk> (raw)
In-Reply-To: <03f501c379a2$b14b49b0$3203a8c0@duke>
On Sad, 2003-09-13 at 03:56, Iker wrote:
> More specifically, I was wondering if the write to the pipe or the call back
> into poll involved anything that might prompt the scheduler to replace the
> thread in this scenario.
Unless it happens to cause page faults or fill up the pipe nothing in
paticular. Sending a message to yourself down a pipe is pretty standard
in event based programs as a way of turning a signal from asynchronous
event and thus nuisance to handle into a message.
next prev parent reply other threads:[~2003-09-13 17:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 1:19 Iker
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 [this message]
2003-09-13 19:37 ` Jamie Lokier
2003-09-15 23:36 ` Robert White
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=1063473005.8519.7.camel@dhcp23.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davids@webmaster.com \
--cc=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®