>zeroed with the cache invalidating or snooping the accesses. May-be having
>some pool of zeroed memory or zeroing some memory is useful for security
>issue, but speaking of pooled or cached objects, we probably want to most
Yes, the _only_ point of the clear_page in the page fault path is
security.
>only zero parts that need to be so. The bzero-mania does not look fine
>programming to me.
Agreed. OTOH using a different chip for the bzero may really improve
performances and scale better.
The bzero-mania with a minimal slowdown under heavy load still doesn't
convince me instead...
>PS: If we want to be able to write zero-filled blocks to a disk without
>bzero overhead, for example, we can reserve a small amount of physical
>pages filled with zeros at startup.
Currently there's at least one page reserved that must stay zeroed all the
time. It's the ZERO_PAGE(). mapping /dev/null always fallback on the
ZERO_PAGE. you can read it as many times and whenever you want.
Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/