mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Neil Brown <neilb@suse.de>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-raid@vger.kernel.org
Subject: Re: [RFC][PATCH -mm][Experimental] suspend: Do not freeze md_threads
Date: Mon, 6 Nov 2006 11:28:18 +0100	[thread overview]
Message-ID: <20061106102818.GA3138@elf.ucw.cz> (raw)
In-Reply-To: <17742.26007.249504.79631@cse.unsw.edu.au>

Hi!

> > > If there's a swap file on a software RAID, it should be possible to use this
> > > file for saving the swsusp's suspend image.  Also, this file should be
> > > available to the memory management subsystem when memory is being freed before
> > > the suspend image is created.
> > > 
> > > For the above reasons it seems that md_threads should not be frozen during
> > > the suspend and the appended patch makes this happen, but then there is the
> > > question if they don't cause any data to be written to disks after the
> > > suspend image has been created, provided that all filesystems are frozen
> > > at that time.
> > 
> > Looks okay to me. It would be nice to have someone (Ingo? Neil?) try
> > to suspend to swap on md......
> 
> Yes... suspending to swap-on-md would probably be fairly easy.
> Resuming from that same swap might be a bit more of a challenge.
> If only I had more time...

With uswsusp (scheduled for 10.2), it should be fairly easy, too. I
guess we shall just get Andrea to try it :-).
							Pavel 
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      reply	other threads:[~2006-11-06 10:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-02 22:55 Rafael J. Wysocki
2006-11-05 11:58 ` Pavel Machek
2006-11-05 22:28   ` Neil Brown
2006-11-06 10:28     ` Pavel Machek [this message]

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=20061106102818.GA3138@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=rjw@sisk.pl \
    /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®