public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Suparna Bhattacharya <suparna@in.ibm.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Nigel Cunningham <ncunningham@clear.net.nz>,
	Linus Torvalds <torvalds@transmeta.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Software Suspend Functionality in 2.5
Date: Fri, 28 Feb 2003 19:09:24 +0530	[thread overview]
Message-ID: <20030228190924.A3034@in.ibm.com> (raw)
In-Reply-To: <20030228130548.GA8498@atrey.karlin.mff.cuni.cz>; from pavel@ucw.cz on Fri, Feb 28, 2003 at 02:05:48PM +0100

On Fri, Feb 28, 2003 at 02:05:48PM +0100, Pavel Machek wrote:
> Hi!
> 
> > Since we've had to work on a solution that can be used 
> > for accurate non-disruptive dumps as well as crash dumps
> > (the latter using kexec), I was wondering whether it 
> > was worth exploring possibilities of commonality with 
> > swsusp down the line ... I know its not probably not 
> > something very immediate, but just an indication on 
> > whether we should keep applicability for swsusp (probably 
> > reuse and share ideas/code back and forth between the 
> > two efforts) in mind as we move forward. Because we 
> > have to support a more restrictive situation when it 
> > comes to dumping, it just may be usable by swsusp too 
> > if we can get it right.
> 
> Well, less code duplication is always welcome. But notice we need
> *atomic* snapshots in swsusp, else we might corrupt data.

Atomic snapshots are what we'd like for dump too, since we desire 
accurate dumps (minimum drift), so its not a conflicting requirement. 
The difference is that while you could do i/o (e.g to flush pages 
to free up memory) before initiating an atomic snapshot, we can't.

Regards
Suparna

-- 
Suparna Bhattacharya (suparna@in.ibm.com)
Linux Technology Center
IBM Software Labs, India


  reply	other threads:[~2003-02-28 13:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-26  5:45 Software Suspend Functionality in 2.5 Nigel Cunningham
2003-02-27 12:42 ` Suparna Bhattacharya
2003-02-27 18:16   ` Nigel Cunningham
2003-02-28  6:47     ` Suparna Bhattacharya
2003-02-28 13:05       ` Pavel Machek
2003-02-28 13:39         ` Suparna Bhattacharya [this message]
2003-02-28 13:44           ` Pavel Machek
2003-02-28 15:18             ` Suparna Bhattacharya
2003-02-28 15:17               ` Pavel Machek
2003-02-28 18:59                 ` Nigel Cunningham
2003-03-03  4:28                   ` Suparna Bhattacharya
2003-03-03  6:36                     ` Nigel Cunningham
2003-03-03  6:54                       ` Suparna Bhattacharya
2003-03-03 10:49                         ` Nigel Cunningham
2003-03-03 12:25                         ` Pavel Machek
2003-03-03 13:06                           ` Suparna Bhattacharya

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=20030228190924.A3034@in.ibm.com \
    --to=suparna@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@clear.net.nz \
    --cc=pavel@ucw.cz \
    --cc=torvalds@transmeta.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