| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <45EA0C3D.1010001@redhat.com> Date: Sat, 03 Mar 2007 19:01:01 -0500 From: Rik van Riel <riel@...hat.com> To: Andrew Morton <akpm@...ux-foundation.org> CC: linux-kernel@...r.kernel.org Subject: Re: userspace pagecache management tool Andrew Morton wrote: > On Sat, 03 Mar 2007 17:25:30 -0500 Rik van Riel <riel@...hat.com> wrote: > >> backup program > > A suitable policy for a backup program would probably be to invalidate any > output file(s) and to invalidate those pages of the input files which were > not in cache when the backup program first opened those files. That way > the backup program will have no effect on the cache state, except for the > race situation where someone read an uncached file while the backup program > was reading from it too. The use-once policy we have in the kernel should work perfectly fine for backups. All we need to do is actually honor the accessed bit on active page cache pages, instead of flushing them onto the inactive list. What am I overlooking? > This can be added in an hour or two with no kernel changes (use mincore). mincore only works for mmaped areas, we'd need an fincore to work with file handles. -- Politics is the struggle between those who want to make their country the best in the world, and those who believe it already is. Each group calls the other unpatriotic. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists