From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH 3/4] block, documentation: Explain the word 'segments'
Date: Fri, 28 Jun 2019 16:14:07 -0400 [thread overview]
Message-ID: <yq1tvc9h3hs.fsf@oracle.com> (raw)
In-Reply-To: <20190628200745.206110-4-bvanassche@acm.org> (Bart Van Assche's message of "Fri, 28 Jun 2019 13:07:44 -0700")
Bart,
> Several block layer users who are not kernel developers do not know
> that the word 'segment' refers to an element in a DMA scatter/gather
> list. Make the block layer documentation easier to understand by
> stating explicitly what the word 'segment' stands for.
I don't have a problem clarifying the documentation. But the sysfs knobs
have a "segment" suffix so for better or for worse it is part of the
block layer lingo.
Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-06-28 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 20:07 [PATCH 0/4] Improve block layer request queue sysfs parameter documentation Bart Van Assche
2019-06-28 20:07 ` [PATCH 1/4] block, documentation: Fix wbt_lat_usec documentation Bart Van Assche
2019-06-28 20:22 ` Martin K. Petersen
2019-06-28 20:07 ` [PATCH 2/4] block, documentation: Sort queue sysfs attribute names alphabetically Bart Van Assche
2019-06-28 20:22 ` Martin K. Petersen
2019-06-28 20:07 ` [PATCH 3/4] block, documentation: Explain the word 'segments' Bart Van Assche
2019-06-28 20:14 ` Martin K. Petersen [this message]
2019-06-28 20:07 ` [PATCH 4/4] block, documentation: Document discard_zeroes_data, fua, max_discard_segments and write_zeroes_max_bytes Bart Van Assche
2019-06-28 20:23 ` Martin K. Petersen
2019-06-29 15:38 ` [PATCH 0/4] Improve block layer request queue sysfs parameter documentation Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yq1tvc9h3hs.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.