From: Sagi Grimberg <sagi@grimberg.me>
To: Guixin Liu <kanie@linux.alibaba.com>, hch@lst.de, kch@nvidia.com
Cc: linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvmet-rdma: remove NVMET_RDMA_REQ_INVALIDATE_RKEY flag
Date: Wed, 20 Mar 2024 12:45:08 +0200 [thread overview]
Message-ID: <bca94901-3d77-4779-851f-d121efff3fbf@grimberg.me> (raw)
In-Reply-To: <20240320092035.22546-1-kanie@linux.alibaba.com>
On 20/03/2024 11:20, Guixin Liu wrote:
> We can simply use invalidate_rkey to check instead of adding a flag.
>
> Signed-off-by: Guixin Liu <kanie@linux.alibaba.com>
> ---
> drivers/nvme/target/rdma.c | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/nvme/target/rdma.c b/drivers/nvme/target/rdma.c
> index f2bb9d95ecf4..d0bc72c75471 100644
> --- a/drivers/nvme/target/rdma.c
> +++ b/drivers/nvme/target/rdma.c
> @@ -53,7 +53,6 @@ struct nvmet_rdma_cmd {
>
> enum {
> NVMET_RDMA_REQ_INLINE_DATA = (1 << 0),
> - NVMET_RDMA_REQ_INVALIDATE_RKEY = (1 << 1),
> };
>
> struct nvmet_rdma_rsp {
> @@ -722,7 +721,7 @@ static void nvmet_rdma_queue_response(struct nvmet_req *req)
> struct rdma_cm_id *cm_id = rsp->queue->cm_id;
> struct ib_send_wr *first_wr;
>
> - if (rsp->flags & NVMET_RDMA_REQ_INVALIDATE_RKEY) {
> + if (rsp->invalidate_rkey) {
> rsp->send_wr.opcode = IB_WR_SEND_WITH_INV;
> rsp->send_wr.ex.invalidate_rkey = rsp->invalidate_rkey;
> } else {
> @@ -905,10 +904,8 @@ static u16 nvmet_rdma_map_sgl_keyed(struct nvmet_rdma_rsp *rsp,
> goto error_out;
> rsp->n_rdma += ret;
>
> - if (invalidate) {
> + if (invalidate)
> rsp->invalidate_rkey = key;
> - rsp->flags |= NVMET_RDMA_REQ_INVALIDATE_RKEY;
> - }
>
> return 0;
>
Who clears invalidate_rkey between executions?
I think you need to clear right after nvmet_rdma_get_rsp()
next prev parent reply other threads:[~2024-03-20 10:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-20 9:20 [PATCH] nvmet-rdma: remove NVMET_RDMA_REQ_INVALIDATE_RKEY flag Guixin Liu
2024-03-20 10:45 ` Sagi Grimberg [this message]
2024-03-20 10:56 ` Guixin Liu
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=bca94901-3d77-4779-851f-d121efff3fbf@grimberg.me \
--to=sagi@grimberg.me \
--cc=hch@lst.de \
--cc=kanie@linux.alibaba.com \
--cc=kch@nvidia.com \
--cc=linux-nvme@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox