Chris Mason <chris.mason@xxxxxxxxxx> writes: > On Wednesday 16 April 2008, Andi Kleen wrote: >> Chris Mason <chris.mason@xxxxxxxxxx> writes: >> > The async work queues include code to checksum data pages without the FS >> > mutex >> >> Are they able to distribute work to other cores? > > Yes, it just uses a workqueue. Unfortunately work queues don't do that by default currently. They tend to process on the current CPU only. > The current implemention is pretty simple, it > surely could be more effective at spreading the work around. > > I'm testing a variant that only tosses over to the async queue for pdflush, > inline reclaim should stay inline. Longer term I would hope that write checksum will be basically free by doing csum-copy at write() time. The only problem is just where to store the checksum between the write and the final IO? There's no space in struct page. The same could be also done for read() but that might be a little more tricky because it would require delayed error reporting and it might be difficult to do this for partial blocks? -Andi -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
