Sorry. I'm not sure what you mean. Are you saying that if I had a
doctored FS, then it would be a lot faster? If so, how much? What are
your boot times?
> > > The theory was lovely. And I tried all sorts of stuff. But
> > > the bottom line benefit was only about 10%. The whole thing
> > > was constrained by buffercache seek time - filesytem metadata.
> >
> > The problem is that you're not listing the metadata blocks when
> > building the database, right? And that's because Linus didn't want
> > such hackery in the kernel. So instead we got the not-very-useful
> > readahead system call.
>
> No, everything was listed. pagecache, buffercache. This
> was pre buffercache-in-pagecache. I tried lots of stuff,
> including intermingling pagecache and buffercache reads
> in strict LBA order, buffercache first, no buffercache at
> all. Nothing really helped. Fact is, all those files are
> sprinkled all over the disk and a short seek is pretty much
> as expensive as a long one.
Bugger.
> > Of course, my boot scripts do the dependency stuff right (actually,
> > it's the changes I made to simpleinit(8) that make it possible).
>
> Yes, I've looked. It's nice stuff. The dependencies are critial.
<blush> Thanks.
> One thing I did do a while back was to set up a new root filesystem
> on a new disk via `tar cf - | (cd /newplace ; tar xf -)'. But
> before doing this I nobbled ext2's directory placement algorithm so
> subdirectories in the new fs go in the same blockgroup as the
> parent. This sped boots up quite a bit. Probably the pagecache
> preload code would work better with that setup.
Yeah. I guess this nobbling isn't likely to make it into the kernel. I
should fiddle with tar sometime to create everything in the one
directory and move stuff around to the final destination. That would
get around the ext2fs placement misfeature (in this context, anyway).
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
-
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/