> Swapping is an important case. But 9 times out of 10 you are managing
> memory in caches, and throwing unused pages into swap. You aren't
> busily paging the data back an forth. But if I have to make a choice
> in what kind of situation I want to take a performance hit, paging
> approaching thrashing or a system whose working set size is well
> within RAM. I'd rather take the hit in the system that is paging.
> Besides I also like to run a lot of shell scripts, which again stress
> the fork()/exec()/exit() path.
> So no I don't think keeping those paths fast is silly.
Ben and I have already been thinking a bit about memory
objects, so we have both reverse mappings AND we can skip
copying the page tables at fork() time (needing to clear
less at the subsequent exec(), too) ...
Of course this means I'll throw away my pte-based reverse
mapping code and will look at an object-based reverse mapping
scheme like Ben made for 2.1 and DaveM made for 2.3 ;)
-- IA64: a worthy successor to i860.
Send all your spam to email@example.com (spam digging piggy)
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/