From: Pavel Machek <pavel@suse.cz>
To: Jens Axboe <axboe@suse.de>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: suspend.c: This is broken, fixme
Date: Mon, 3 Jun 2002 13:32:21 +0200 [thread overview]
Message-ID: <20020603113221.GA17228@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20020603095507.GA3030@elf.ucw.cz> <20020603110816.GI820@suse.de>
Hi!
> > @@ -300,7 +301,8 @@
> > static void do_suspend_sync(void)
> > {
> > while (1) {
> > - run_task_queue(&tq_disk);
> > + blk_run_queues();
> > +#error this is broken, FIXME
> > if (!TQ_ACTIVE(tq_disk))
> > break;
> >
> > . Why is it broken?
>
> Hey, I even cc'ed you on the patch when it went to Linus... Lets
> look at
Okay; I thought I corrected it in the meantime, that's why I got confused.
> what happened before: run tq_disk, then check if it is active. What
> prevents tq_disk from being active right after you issue the TQ_ACTIVE
> check? Nothing. And I'm not sure exactly what semantics you think
> running tq_disk has. I suspect you are looking for a 'start any pending
> i/o and return when it has completed', which is far from what happens.
> Running tq_disk will _try_ to start _some_ I/O, and eventually, in time,
> the currently pending requests will have completed. In the mean time,
> more I/O could have been added though.
I'm alone at the system at that point. All user tasks are stopped and
I'm only thread running. There's noone that could submit requests at
that point.
In such case, killing #error is right solution, right?
Pavel
--
Casualities in World Trade Center: ~3k dead inside the building,
cryptography in U.S.A. and free speech in Czech Republic.
next prev parent reply other threads:[~2002-06-03 11:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 9:55 Pavel Machek
2002-06-03 11:08 ` Jens Axboe
2002-06-03 11:32 ` Pavel Machek [this message]
2002-06-03 11:35 ` Jens Axboe
2002-06-03 12:13 ` Pavel Machek
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=20020603113221.GA17228@atrey.karlin.mff.cuni.cz \
--to=pavel@suse.cz \
--cc=axboe@suse.de \
--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®