From: Leon Romanovsky <leonro@nvidia.com>
To: Daisuke Matsuda <matsuda-daisuke@fujitsu.com>
Cc: <jgg@nvidia.com>, <zyjzyj2000@gmail.com>, <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH v2] RDMA/rxe: Delete error messages triggered by incoming Read requests
Date: Wed, 31 Aug 2022 09:57:51 +0300 [thread overview]
Message-ID: <Yw8Gb9urH63oHETq@unreal> (raw)
In-Reply-To: <20220829071218.1639065-1-matsuda-daisuke@fujitsu.com>
On Mon, Aug 29, 2022 at 04:12:18PM +0900, Daisuke Matsuda wrote:
> An incoming Read request causes multiple Read responses. If a user MR to
> copy data from is unavailable or responder cannot send a reply, then the
> error messages can be printed for each response attempt, resulting in
> message overflow.
>
> Signed-off-by: Daisuke Matsuda <matsuda-daisuke@fujitsu.com>
> ---
> v2
> Stop passing unused value to 'err', as commented by Cheng Xu
>
> drivers/infiniband/sw/rxe/rxe_resp.c | 10 +++-------
> 1 file changed, 3 insertions(+), 7 deletions(-)
>
Thanks, applied.
prev parent reply other threads:[~2022-08-31 6:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 7:12 [PATCH v2] RDMA/rxe: Delete error messages triggered by incoming Read requests Daisuke Matsuda
2022-08-31 6:57 ` Leon Romanovsky [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=Yw8Gb9urH63oHETq@unreal \
--to=leonro@nvidia.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=matsuda-daisuke@fujitsu.com \
--cc=zyjzyj2000@gmail.com \
/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