![]() | |||||||||||||
Messages in this thread |
Hi, On Sat, 2003-01-04 at 11:11, Andrew Morton wrote: > This is because of differences in how sync() is handled between 2.4.20's > ext3 and 2.4.21-pre2's. > > 2.4.21-pre2: > > sync() will start the commit, and will wait on it. So you know that > when it returns, everything which was dirty is now tight on disk. > > So yes, running a looping sync while someone else is writing stuff > will take much longer in 2.4.21-pre2, because that kernel actually > waits on the writeout. Actually, I'm wondering if we should back that particular bit out. For a user with a hundred mounted filesystems, syncing each one in order, sequentially, is going to suck (and we don't currently have a simple way in 2.4 to detect which syncs are on separate spindles and so can be parallelised.) --Stephen - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 12:32 [from the cache] ©2003-2008 | |||||||||||||