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 17:36:44 +0100 [thread overview]
Message-ID: <20050208163644.GG1622@elf.ucw.cz> (raw)
In-Reply-To: <1107822206.2756.18.camel@desktop.cunninghams>
Hi!
> I'm keen to see if we can merge Suspend2's freezer implementation after
> 2.6.11. Does that conflict with any of your intended changes? If it
> doesn't, I'll submit a patch for review/merge as quickly as I can.
Freezer is very independend, and no, I do not plan any changes in that area.
> 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?
> 1) Freeze user space threads without SYNCTHREAD set;
> 2) Freeze user space threads with SYNCTHREAD set;
> 3) Run our own sys_sync in case no one else was syncing
> 4) Freeze kernel space threads without NOFREEZE set.
>
> I'd also like to look at your SMP support and see if we can improve
> compatibility there at the same time.
Why not... But parts of smp support really need to be in assembly, and
they are not, neither in swsusp nor in suspend2...
> Finally I'd like to merge the support for freezer flags on workqueues.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
next prev parent reply other threads:[~2005-02-08 16:37 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 [this message]
2005-02-08 21:59 ` Nigel Cunningham
2005-02-08 22:32 ` Pavel Machek
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=20050208163644.GG1622@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