From: Jason Gunthorpe <jgg@ziepe.ca>
To: Max Gurtovoy <maxg@mellanox.com>
Cc: linux-rdma@vger.kernel.org, dledford@redhat.com,
leonro@mellanox.com, sagi@grimberg.me
Subject: Re: [PATCH 1/1] IB/iser: add unlikely checks in the fast path
Date: Tue, 1 Oct 2019 11:29:29 -0300 [thread overview]
Message-ID: <20191001142929.GA11407@ziepe.ca> (raw)
In-Reply-To: <1569274369-29217-1-git-send-email-maxg@mellanox.com>
On Tue, Sep 24, 2019 at 12:32:49AM +0300, Max Gurtovoy wrote:
> ib_post_send, ib_post_recv and ib_dma_map_sg operations should succeed
> unless something unusual happened to the ib device.
>
> Signed-off-by: Max Gurtovoy <maxg@mellanox.com>
> Acked-by: Sagi Grimberg <sagi@grimberg.me>
> ---
> drivers/infiniband/ulp/iser/iser_memory.c | 2 +-
> drivers/infiniband/ulp/iser/iser_verbs.c | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
Applied to for-next, thanks
Jason
prev parent reply other threads:[~2019-10-01 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 21:32 [PATCH 1/1] IB/iser: add unlikely checks in the fast path Max Gurtovoy
2019-09-23 22:02 ` Sagi Grimberg
2019-10-01 14:29 ` Jason Gunthorpe [this message]
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=20191001142929.GA11407@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dledford@redhat.com \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=maxg@mellanox.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).