Re: [dm-devel] REQUEST for new 'topology' metrics to be moved out of the 'queue' sysfs directory.

On Thursday June 25, martin.petersen@xxxxxxxxxx wrote:
"Neil" == NeilBrown <neilb@xxxxxxx> writes:

And just to make it clear: I completely agree with your argument that
which knob to choose is I/O size dependent. My beef with your proposal
is that I believe the length of the list should be 2.

0, 1, or infinity are the only credible sizes for this sort of list.

However I feel I've written enough on this particular issue (the
particular meaning of the various fields, not the directory location
which I still feel strongly about).

Providing the fields are clearly and unambiguously documented so that
it I can use the documentation to verify the implementation (in md at
least), I will be satisfied. And if the names of the files actually
match the documented meaning (so e.g. s/io/write/) I might even be
happy.

I'm looking forward to seeing how you justify the name
"physical_block_size" in a way the encompasses possibilities like a
device that stripes over a heterogeneous set of disk drives ;-)

Thanks,
NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: WriteFile()
    ... whether the I/O is synchronous or asynchronous doesn't change anything. ... With a direct-access storage device file, one can expect that WriteFile ... The ReadFile() analogy was poor and finally, ... >> documentation on the expected behavior of Read/WriteFile. ...
    (microsoft.public.win32.programmer.kernel)
  • Re: PNG and Fortran
    ... [implement some form of stream I/O]? ... as not a big fan of that documentation. ... There is always the fallback of "ordinary" unformatted direct access, ...
    (comp.lang.fortran)
  • Re: prototype.js (was Re: Ajax Timeouts)
    ... Having used and become dependent on its syntax, ... Some other attempts at documentation: ... There is no support community or blog of any real substance ... for feature detection. ...
    (comp.lang.javascript)
  • Re: Tiny ARM Development
    ... Merely reading and writing to I/O ports, ... All I/O is memory mapped, ARM does not have a separate I/O address ... The instruction set documentation is published by ARM, not Atmel, but a ...
    (comp.arch.embedded)
  • Re: [patch 8/8] fs: add i_op->sync_inode
    ... Could you perhaps give a bit more detail in the documentation about ... file system is still using the buffer cache for data I/O) and/or the ... data has been pushed to the block I/O system, ...
    (Linux-Kernel)