2.6 swapping behavior
Posted May 14, 2004 11:17 UTC (Fri) by
forthy (guest, #1525)
In reply to:
2.6 swapping behavior by njhurst
Parent article:
2.6 swapping behavior
IMHO the initial priority of a just-allocated or just-loaded buffer is too
high. That's why memory hogs (which claim a page once and never look at it
again) swap out everything else in Linux, and updatedb also does the same
thing. The pages of OpenOffice, which have been used and reused all day
long over and over again have lower priority for the kernel than a newly
allocated use-once page.
But as long as kernel developer stick their thumbs in their ears and sing
"lalala", this won't change.
Another note: updatedb *only* reads the names of a file system. Well, it
also checks if a name is a directory, and that forces it to read the
entire inode. The real problem here is that updatedb tries to solve
something the file system should do itself (especially if you think of it
like Hans Reiser does). Why is it impossible for the file system to keep
the file names in a database like updatedb, and answer queries like locate
directly? Hint: BeOS did something like that.
(
Log in to post comments)
