> Any suggestion on what BLKBSZGET should return?
>
> 1) blocksize = 0 (same as it does already for most devices)
This is what tools like df expect
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Thursday 19 July 2007, Christoph Hellwig wrote:
>
> > None of these seems to make any difference whatsoever, except for BLKBSZGET
> > returning non-zero on a ramdisk or dcssblk device. I think we'd be best
> > off removing bd_block_size from the kernel altogether, and I'll remove
> > it from
On Thursday 19 July 2007, Christoph Hellwig wrote:
None of these seems to make any difference whatsoever, except for BLKBSZGET
returning non-zero on a ramdisk or dcssblk device. I think we'd be best
off removing bd_block_size from the kernel altogether, and I'll remove
it from the
Any suggestion on what BLKBSZGET should return?
1) blocksize = 0 (same as it does already for most devices)
This is what tools like df expect
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
4 matches
Mail list logo
