Messages in this thread | | | Date | Thu, 23 Feb 2006 01:33:00 +0100 | From | Pavel Machek <> | Subject | Re: Which is simpler? (Was Re: [Suspend2-devel] Re: [ 00/10] [Suspend2] Modules support.) |
| |
Hi!
> > > > > The fact that we use page flags to store some suspend/resume-related > > > > > information is a big disadvantage in my view, and I'd like to get rid > > > > > of that in the future. In principle we could use a bitmap, or rather > > > > > two of them, to store the same information independently of the page > > > > > flags, and if we use bitmaps for this purpose, we can use them also > > > > > instead of PBEs. > > > > > > > > Well, we "only" use 2 bits... :-). > > > > > > In my view the problem is this adds constraints that other people have to > > > take into account. Not a good thing if avoidable IMHO. > > > > Well, I hope that swsusp development will move to userland in future > > > > :-). > > I don't get your point. I mean, we're talking about flags that record what > pages are going to be in the image, be atomically copied and so on. Are you > planning on trying to export the free page information and the like to > userspace too, along with atomic copy code?
No, certainly not.
Rafael said something like "being limited is bad, because it makes it hard to change in-kernel snapshoting code". My reply was something like "I hope people will stop changing in-kernel swsusp code, and hack userland instead".
Atomic copy code has to stay with kernel: it needs disabled interrupts, access to all the RAM, etc. It screams "kernel code".
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/
| |