Re: [PATCH] 64 bit scsi read/write

["Ragnar Kjørstad" <kernel@ragnark.vestdata.no>]

> Cheers, Andreas
> ---------------
> *) For ext3, you need enough extra space for the superblock, group descriptors,
>    one block and inode bitmap, the first inode table, (and lost+found if
>    you don't want to do extra work deleting lost+found before creating the
>    journal, and re-creating it afterwards).  The output from "dumpe2fs"
>    will tell you the number of inode blocks and group descriptor blocks.
>    For reiserfs it is hard to tell exactly where the file will go, but if
>    you had, say, a 64MB NVRAM device and a new filesystem, you could expect
>    the journal to be put entirely on the NVRAM device.

You can use the LVM tools to see what extents are written the most times
- I'm sure that after having used the filesystem a little bit it will be
clear wich extents hold the journal. (and then you can move them to
NVRAM).

For reiserfs, I believe you can no specify a seperate device for your
journal and don't need lvm. Not sure if this code entered the kernel yet
though - maybe you need a patch.


When doing you testing, you should be aware that the results will be
very much dependent on the device you use for the filesystem. One thing
is that if you use a slow ide-drive, then the NVRAM/disk performance
will be higher than if you used a fast scsi-drive. But more importantly,
if you use a highend RAID, it will include NVRAM of it's own. So if you
really want to know if seperate NVRAM makes sense for you highend
server - don't test this on a regular disk and assume the results will
be the same.




-- 
Ragnar Kjorstad
Big Storage