All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nitesh Shetty <nj.shetty@samsung.com>
To: Keith Busch <kbusch@meta.com>
Cc: axboe@kernel.dk, hch@lst.de, linux-block@vger.kernel.org,
	linux-nvme@lists.infradead.org, linux-fsdevel@vger.kernel.org,
	io-uring@vger.kernel.org, sagi@grimberg.me,
	asml.silence@gmail.com, anuj20.g@samsung.com,
	joshi.k@samsung.com, Hannes Reinecke <hare@suse.de>,
	Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCHv13 05/11] block: expose write streams for block device nodes
Date: Wed, 11 Dec 2024 11:23:54 +0530	[thread overview]
Message-ID: <20241211055354.ozous6df7gpgjcpp@ubuntu> (raw)
In-Reply-To: <20241210194722.1905732-6-kbusch@meta.com>

[-- Attachment #1: Type: text/plain, Size: 465 bytes --]

On 10/12/24 11:47AM, Keith Busch wrote:
>From: Christoph Hellwig <hch@lst.de>
>
>Use the per-kiocb write stream if provided, or map temperature hints to
>write streams (which is a bit questionable, but this shows how it is
>done).
>
>Reviewed-by: Hannes Reinecke <hare@suse.de>
>Signed-off-by: Christoph Hellwig <hch@lst.de>
>[kbusch: removed statx reporting]
>Signed-off-by: Keith Busch <kbusch@kernel.org>
>---

Reviewed-by: Nitesh Shetty <nj.shetty@samsung.com>

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2024-12-11  6:05 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-10 19:47 [PATCHv13 00/11] block write streams with nvme fdp Keith Busch
2024-12-10 19:47 ` [PATCHv13 01/11] fs: add a write stream field to the kiocb Keith Busch
2024-12-10 19:47 ` [PATCHv13 02/11] block: add a bi_write_stream field Keith Busch
2024-12-10 19:47 ` [PATCHv13 03/11] block: introduce max_write_streams queue limit Keith Busch
2024-12-10 19:47 ` [PATCHv13 04/11] block: introduce a write_stream_granularity " Keith Busch
2024-12-11  8:46   ` John Garry
2024-12-10 19:47 ` [PATCHv13 05/11] block: expose write streams for block device nodes Keith Busch
2024-12-11  5:53   ` Nitesh Shetty [this message]
2024-12-10 19:47 ` [PATCHv13 06/11] io_uring: enable per-io write streams Keith Busch
2024-12-11  6:44   ` Nitesh Shetty
2024-12-10 19:47 ` [PATCHv13 07/11] nvme: add a nvme_get_log_lsi helper Keith Busch
2024-12-10 19:47 ` [PATCHv13 08/11] nvme: pass a void pointer to nvme_get/set_features for the result Keith Busch
2024-12-10 19:47 ` [PATCHv13 09/11] nvme: add FDP definitions Keith Busch
2024-12-10 19:47 ` [PATCHv13 10/11] nvme: register fdp parameters with the block layer Keith Busch
2024-12-11  6:41   ` Nitesh Shetty
2024-12-11  9:30   ` John Garry
2024-12-11 15:55     ` Keith Busch
2024-12-11 11:23   ` Hannes Reinecke
2024-12-11 14:40   ` kernel test robot
2024-12-11 17:18   ` kernel test robot
2024-12-10 19:47 ` [PATCHv13 11/11] nvme: use fdp streams if write stream is provided Keith Busch
2024-12-11  7:13 ` [PATCHv13 00/11] block write streams with nvme fdp Christoph Hellwig
2024-12-12  5:51   ` Kanchan Joshi
2024-12-12  6:05     ` Christoph Hellwig

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=20241211055354.ozous6df7gpgjcpp@ubuntu \
    --to=nj.shetty@samsung.com \
    --cc=anuj20.g@samsung.com \
    --cc=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=io-uring@vger.kernel.org \
    --cc=joshi.k@samsung.com \
    --cc=kbusch@kernel.org \
    --cc=kbusch@meta.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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.