Messages in this thread | | | Date | Fri, 10 Feb 2006 00:34:06 +0100 | From | Pavel Machek <> | Subject | Re: Which is simpler? (Was Re: [Suspend2-devel] Re: [ 00/10] [Suspend2] Modules support.) |
| |
Hi!
> > > Any changes to userspace are a fair game. OTOH kernel provides linear > > > image to be saved to userspace, and what it uses internally should not > > > be important to userland parts. (And Rafael did some changes in that > > > area to make it more effective, IIRC). > > > > Yes. The code is now split into the part that handles the snapshot image > > (in snapshot.c) and the part that writes/reads it to swap (in swap.c). [I'm > > referring to recent -mm kernels.] > > > > The access to the snapshot image is provided via the functions > > snapshot_write_next() and snapshot_read_next() that are called by the > > code in swap.c and may be used by the user space tools via the > > interface in user.c. In principle it ought to be possible to plug > > something else instead of the code in snapshot.c without > > breaking the rest. > > So, what is the answer then? If I submitted patches to provide the possibility > of separating LRU pages into a separate stream of pages to be read/written, > would it have any chance of getting merged? (Along with other patches to make > writing a full image of memory possible).
Could we do the other stuff, first, please? Userland LZF/encryption/progress should be easy to do, and doing that should teach us how to cooperate. Pavel -- Web maintainer for suspend.sf.net (www.sf.net/projects/suspend) wanted... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |