| |||||||||||||
Garrett: ext4, application expectations and power managementGarrett: ext4, application expectations and power managementPosted Mar 16, 2009 10:52 UTC (Mon) by MathFox (guest, #6104)In reply to: Garrett: ext4, application expectations and power management by michaeljt Parent article: Garrett: ext4, application expectations and power management
Michael, Yes, the kernel could do it, but such a log would have to be written to disk... But then it would be more efficient to directly write that log directly to the file system.
You'll create similar issues wrt. performance and commit intervals with a kernel-based log, but with the added overhead of writing data twice.
(Log in to post comments)
Garrett: ext4, application expectations and power management Posted Mar 16, 2009 10:54 UTC (Mon) by michaeljt (subscriber, #39183) [Link]
Would that apply even if the blocks for the log were reserved in advance and their location known to the kernel?
Garrett: ext4, application expectations and power management Posted Mar 16, 2009 10:55 UTC (Mon) by michaeljt (subscriber, #39183) [Link]
I will answer my own question - presumably yes, because the kernel can't assume that the filesystem does a simple block to disk mapping.
|
|||||||||||||