> I would love to move inode metadata to the page cache. That would simplify
> so much in the NTFS driver and would result in an incredible speed boost
> due to getting rid of all the silly copying of data back and forth inside
> the driver as we could just pass pointers around instead (to lock
> Yes and no. They will be uncompressed but not when opening the inode. It
> will be "uncompress required extent's run list on demand".
Are you sure this can work? Initially, I thought I could use the
attribute list to only uncompress the extend that has the VCN I'm
interested in.
That would no
> >That would not work: NT would split individual runs across extends
> >(i.e. split them in the middle). Did I misunderstand, or do you have a
> >solution for that as well.
> >
> Are you sure that it's true? My NTFS resizer interprets parts of runlist
> stored in different FILE records independe
> > Anyone know about 3.1?
> >
>
> It's an HPFS variant.
No. NT was using NTFS right from the start.
Regards,
Martin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-
4 matches
Mail list logo
