From: Pavel Machek <pavel@suse.cz>
To: Stefan Rompf <stefan@loplof.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] userland swsusp
Date: Wed, 16 Nov 2005 19:07:16 +0000 [thread overview]
Message-ID: <20051116190715.GF2193@spitz.ucw.cz> (raw)
In-Reply-To: <200511161700.27239.stefan@loplof.de>
Hi!
> > This is prototype of userland swsusp. I'd like kernel parts to go in,
> > probably for 2.6.16. Now, I'm not sure about the interface, ioctls are
> > slightly ugly, OTOH it would be probably overkill to introduce
> > syscalls just for this. (I'll need to add an ioctl for freeing memory
> > in future).
>
> I'm curious on the restrictions the userspace part would have to accept.
> Can /usr/swsusp.c write to a file? Currently, you allow it, but I doubt
No. Writing to file would trash the filesystem. But you can bmap the file,
then write to the block device.
> whether it would be wise to write to a file after you've snapshotted
> kernel's filesystem state. OTOH, I don't want to reserve a partition just
> for the image. Can userspace allocate memory after ioctl(SYS_FREEZE)?
Better avoid memory allocation.
> I have userspace supported encryption of the image in mind.
Yes, that should be feasible.
Pavel
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2005-11-16 19:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 16:00 [RFC] userland swsusp Stefan Rompf
2005-11-16 19:07 ` Pavel Machek [this message]
2005-11-17 7:19 ` Stefan Rompf
2005-11-17 10:01 ` Pavel Machek
2005-11-21 6:23 ` Rob Landley
2005-11-21 14:14 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2005-11-15 21:29 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=20051116190715.GF2193@spitz.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=stefan@loplof.de \
/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