From: Sagi Grimberg <sagi@grimberg.me>
To: Potnuri Bharat Teja <bharat@chelsio.com>
Cc: "nab@linux-iscsi.org" <nab@linux-iscsi.org>,
"target-devel@vger.kernel.org" <target-devel@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH RFC] iser-target: avoid reinitializing rdma contexts for isert commands
Date: Mon, 4 Dec 2017 20:31:14 +0200 [thread overview]
Message-ID: <b0a79c32-6820-e3ab-325d-43f0c1b3a839@grimberg.me> (raw)
In-Reply-To: <20171130103450.GA4185@chelsio.com>
> Hi Sagi,
> Thanks for the review.
> The post recv duplication is already handled as a part of "Queue full response
> handling" changes, Here is the patch that handles it:
> https://patchwork.kernel.org/patch/9639185/
Right, forgot about that.
So looks fine to me,
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
WARNING: multiple messages have this Message-ID (diff)
From: Sagi Grimberg <sagi@grimberg.me>
To: Potnuri Bharat Teja <bharat@chelsio.com>
Cc: "nab@linux-iscsi.org" <nab@linux-iscsi.org>,
"target-devel@vger.kernel.org" <target-devel@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH RFC] iser-target: avoid reinitializing rdma contexts for isert commands
Date: Mon, 04 Dec 2017 18:31:14 +0000 [thread overview]
Message-ID: <b0a79c32-6820-e3ab-325d-43f0c1b3a839@grimberg.me> (raw)
In-Reply-To: <20171130103450.GA4185@chelsio.com>
> Hi Sagi,
> Thanks for the review.
> The post recv duplication is already handled as a part of "Queue full response
> handling" changes, Here is the patch that handles it:
> https://patchwork.kernel.org/patch/9639185/
Right, forgot about that.
So looks fine to me,
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
next prev parent reply other threads:[~2017-12-04 18:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 18:28 [PATCH RFC] iser-target: avoid reinitializing rdma contexts for isert commands Potnuri Bharat Teja
2017-11-28 18:40 ` Potnuri Bharat Teja
2017-11-29 22:50 ` Sagi Grimberg
2017-11-29 22:50 ` Sagi Grimberg
2017-11-30 10:34 ` Potnuri Bharat Teja
2017-11-30 10:46 ` Potnuri Bharat Teja
2017-12-04 18:31 ` Sagi Grimberg [this message]
2017-12-04 18:31 ` Sagi Grimberg
2017-12-13 17:51 ` [RFC] " Jason Gunthorpe
2017-12-13 17:51 ` Jason Gunthorpe
2017-12-13 18:48 ` Potnuri Bharat Teja
2017-12-13 18:49 ` Potnuri Bharat Teja
2017-12-18 23:14 ` Jason Gunthorpe
2017-12-18 23:14 ` Jason Gunthorpe
[not found] ` <20171218231439.GA31621-uk2M96/98Pc@public.gmane.org>
2018-01-13 6:20 ` Nicholas A. Bellinger
2018-01-13 6:20 ` Nicholas A. Bellinger
[not found] ` <1515824443.24576.108.camel-XoQW25Eq2zs8TOCF0fvnoXxStJ4P+DSV@public.gmane.org>
2018-01-13 18:04 ` Jason Gunthorpe
2018-01-13 18:04 ` Jason Gunthorpe
2018-01-14 9:26 ` Sagi Grimberg
2018-01-14 9:26 ` Sagi Grimberg
[not found] ` <143bd378-193e-0bbd-1ee3-25299af61aa8-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2018-01-14 18:23 ` Jason Gunthorpe
2018-01-14 18:23 ` Jason Gunthorpe
[not found] ` <20180114182344.GB9088-uk2M96/98Pc@public.gmane.org>
2018-01-15 4:39 ` Nicholas A. Bellinger
2018-01-15 4:39 ` Nicholas A. Bellinger
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=b0a79c32-6820-e3ab-325d-43f0c1b3a839@grimberg.me \
--to=sagi@grimberg.me \
--cc=bharat@chelsio.com \
--cc=linux-rdma@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=target-devel@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.