On Tue, May 02, 2006 at 09:10:01PM +0200, Pavel Machek wrote:
> > $ echo "file /dev/hda1" > /proc/filecache
> > $ cat /proc/filecache
> > # file /dev/hda1
> > # mask 0
> > #
> > # idx len
> > 0 24
> > 48 2
> > 53 5
> > ......
>
> Could we use this instead of blockdev freezing/big suspend image
> support? It should permit us to resume quickly (with small image), and
> then do readahead. ... that will give us usable machine quickly, still
> very responsive desktop after resume?
Badari's usage case inspired me that on suspension we can
- first invoke a user-land tool to do all the cache
status-logging/analyzing/selective-dropping jobs
- then let the kernel write all the remaining caches(made up of many
small chunks) to the suspend image
And do the reverse things on restoring.
With that we moved all the strategies to userspace.
Wu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
