From: erik quanstrom <quanstro@quanstro.net>
To: rvs@sun.com, 9fans@9fans.net
Subject: Re: [9fans] Quick question on stopping a process that waits for IO
Date: Fri, 7 Nov 2008 07:17:45 -0500 [thread overview]
Message-ID: <c36242ab33e54d1d7f3e89888f03cb56@quanstro.net> (raw)
> >> The target process is *already* waiting for the IO stuck inside the
> >> kernel. It is not on a runqueue, not it is considered to be places
> >> there.
> >
> > since procwrite doesn't acquire anything other than the debug lock,
> > how do you know? the proc could start up again before you notice.
>
> How? If there's a stop message already written to /proc/n/ctl. Once
> that is done, the process is guaranteed to be in 2 states and those
> states only: continue waiting for the I/O, being actually Stopped.
> Both of the don't let the scheduler take it to the runqueue.
here's the senerio, i think (works fine on a single processor)
a b
acquire debug lock
sleep complete io
sched
run a bit
syscall
wakeup
- erik
next reply other threads:[~2008-11-07 12:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 12:17 erik quanstrom [this message]
[not found] <507c066f8ade431cfb2d23a36aa82837@quanstro.net>
2008-11-07 18:57 ` Roman V. Shaposhnik
-- strict thread matches above, loose matches on Subject: below --
2008-11-07 11:57 erik quanstrom
2008-11-03 5:55 Roman Shaposhnik
2008-11-04 0:51 ` Roman V. Shaposhnik
2008-11-04 12:34 ` erik quanstrom
2008-11-07 5:51 ` Roman Shaposhnik
2008-11-04 1:01 ` ron minnich
2008-11-05 2:00 ` Roman V. Shaposhnik
2008-11-05 4:00 ` erik quanstrom
2008-11-05 4:47 ` Roman Shaposhnik
2008-11-05 4:01 ` erik quanstrom
2008-11-05 4:22 ` Roman Shaposhnik
2008-11-05 12:55 ` erik quanstrom
2008-11-07 5:48 ` Roman Shaposhnik
2008-11-06 5:40 ` Nathaniel W Filardo
2008-11-07 5:18 ` Roman Shaposhnik
2008-11-07 6:03 ` Nathaniel W Filardo
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=c36242ab33e54d1d7f3e89888f03cb56@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=rvs@sun.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).