From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>
Cc: Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
netdev@vger.kernel.org, Or Har-Toov <ohartoov@nvidia.com>,
Paolo Abeni <pabeni@redhat.com>,
Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>
Subject: Re: [PATCH rdma-next 0/3] Enable IB out-of-order by default in mlx5
Date: Thu, 23 Mar 2023 10:25:35 +0200 [thread overview]
Message-ID: <167955993510.1725006.144017826417177540.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1679230449.git.leon@kernel.org>
On Sun, 19 Mar 2023 14:59:29 +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Hi,
>
> This series from Or changes default of IB out-of-order feature and
> allows to the RDMA users to decide if they need to wait for completion
> for all segments or it is enough to wait for last segment completion only.
>
> [...]
Applied, thanks!
[1/3] net/mlx5: Expose bits for enabling out-of-order by default
https://git.kernel.org/rdma/rdma/c/6e2a3a324aab9d
[2/3] RDMA/mlx5: Disable out-of-order in integrity enabled QPs
https://git.kernel.org/rdma/rdma/c/742948cc02d523
[3/3] net/mlx5: Set out of order (ooo) by default
https://git.kernel.org/rdma/rdma/c/f4244e55e4c3a1
Best regards,
--
Leon Romanovsky <leon@kernel.org>
prev parent reply other threads:[~2023-03-23 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 12:59 [PATCH rdma-next 0/3] Enable IB out-of-order by default in mlx5 Leon Romanovsky
2023-03-19 12:59 ` [PATCH mlx5-next 1/3] net/mlx5: Expose bits for enabling out-of-order by default Leon Romanovsky
2023-03-19 12:59 ` [PATCH rdma-next 2/3] RDMA/mlx5: Disable out-of-order in integrity enabled QPs Leon Romanovsky
2023-03-19 12:59 ` [PATCH mlx5-next 3/3] net/mlx5: Set out of order (ooo) by default Leon Romanovsky
2023-03-23 8:25 ` 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=167955993510.1725006.144017826417177540.b4-ty@kernel.org \
--to=leon@kernel.org \
--cc=edumazet@google.com \
--cc=jgg@ziepe.ca \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ohartoov@nvidia.com \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.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 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.