public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Nigel Cunningham <ncunningham@linuxmail.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Merging the Suspend2 freezer implementation.
Date: Tue, 8 Feb 2005 23:32:41 +0100	[thread overview]
Message-ID: <20050208223241.GC1347@elf.ucw.cz> (raw)
In-Reply-To: <1107899999.4330.39.camel@desktop.cunninghams>

Hi!

> > > The main change involves the introduction of a new SYNCTHREAD flag. We
> > > use this to avoid deadlocking over processes that are running sys_sync
> > > and siblings. Processes that enter those routines get the flag added,
> > > and it's removed when they exit the sync routine. We then freeze in four
> > > stages: 
> > 
> > Is SYNCTHREAD neccessary for me, too, or is it needed for suspend2, only?
> 
> It's necessary for reliable freezing under I/O load. Signalling the
> non-sync threads first removes the race involved in some threads
> submitting I/O while others are trying to sync. Try doing a dd and a
> sync at the same time. The sync can take ages to return, worst case,
> sometimes not until the dd is completed. (Actually, try doing anything
> while a dd is running :>)

Okay, just attach this explanation when you are merging it otherwise
I'll surely ask again...

> > > Finally I'd like to merge the support for freezer flags on workqueues.
> 
> No comment here? :>

:-). I forgot why it was neccessary, but I was too shy to ask
;-). Just attach nice explanation when you attempt to merge it.

								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

  reply	other threads:[~2005-02-08 22:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08  0:23 Merging the Suspend2 freezer implementation Nigel Cunningham
2005-02-08 16:36 ` Pavel Machek
2005-02-08 21:59   ` Nigel Cunningham
2005-02-08 22:32     ` Pavel Machek [this message]
2005-02-08 22:38       ` Nigel Cunningham

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=20050208223241.GC1347@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@linuxmail.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