Messages in this thread | | | Date | Sun, 11 Apr 2004 00:23:47 +0200 (MEST) | From | Szakacsits Szabolcs <> | Subject | Re: Accessing odd last partition sector (was: [Linux-NTFS-Dev] mkntfs dirty volume marking) |
| |
On Sat, 10 Apr 2004 viro@parcelfarce.linux.theplanet.co.uk wrote:
> 2.4 logics around block size handling is broken; we probably could backport > that series of patches, though. 2.6 simply sets block size to GCD(page size, > device size), so we don't have to worry about all that crap.
That's great!
Just one question, in the most common cases the block size ends up between 512 and 4096 bytes. Depending on how this block size used, it can have a significant impact on performance (e.g. 512 vs 4096). Is this true or is it used to be performance independent?
Szaka
- 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/
| |