Christoph Lameter <[EMAIL PROTECTED]> wrote: > > Adds management of ZEROED and NOT_ZEROED pages and a background daemon > called scrubd. /proc/sys/vm/scrubd_load, /proc/sys/vm_scrubd_start and > /proc/sys/vm_scrubd_stop control the scrub daemon. See Documentation/vm/ > scrubd.txt
It's hard to know what to think about this without benchmarking numbers. It would help if you could briefly describe the implementation and design decisions when sending patches. For example, one area where we could use this is in pagetable management, where we need zeroed pages and we tend to free up known-to-be-zero and probably cache-warm pages. Right now some architectures are maintaining their own quicklists, or using a slab cache, both of which are suboptimal. But afaict the patch doesn't differentiate between cache-cold and cache-hot zeroed pages, and doesn't have an API with which clients can free up a known-to-be-zero page. - 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/
