Re: Suspend 2 merge

[Pavel Machek]

Hi!

> Ok, I got it.  I think making LRU safe must sure 
>  1: LRU can't change after saved.
>  2: LRU memory can't change after saved.
> The first one is done, the second we can't sure in current design, can
> we using COW do it?

Userspace processes should be stopped at that point, and you really
can't do COW to kernel users.

> > swsusp1 is more self-contained. As long as drivers stop the DMA and
> > NMI does nothing wrong, atomic snapshot will indeed be atomic.
> Here is my current patch still relative with your bit diff, only core
> part here.
>  1: adding a collide bitmap for speedup collide check, I can't sure
>     four pages is enough, pavel please check.
>  2: swith list_for_xxx style
>  3: corrent calc_nums.

Heh, can you try this after resume?

cat `cat [0-9]*/maps | grep / | sed 's:.* /:/:' | sort -u` > /dev/null

It should have very similar effect to saving LRU, just in one line of
code ;-).

								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/