From: Jason Gunthorpe <jgg@ziepe.ca>
To: Haris Iqbal <haris.iqbal@ionos.com>
Cc: Bob Pearson <rpearsonhpe@gmail.com>,
Li Zhijian <lizhijian@fujitsu.com>,
Yanjun Zhu <yanjun.zhu@linux.dev>,
linux-rdma@vger.kernel.org, Leon Romanovsky <leon@kernel.org>,
Guoqing Jiang <guoqing.jiang@linux.dev>
Subject: Re: [RESEND RFC PATCH for-next] Revert "RDMA/rxe: Create duplicate mapping tables for FMRs"
Date: Fri, 22 Jul 2022 12:13:43 -0300 [thread overview]
Message-ID: <20220722151343.GA55077@ziepe.ca> (raw)
In-Reply-To: <CAJpMwygwvi=CfJmtgienyfPJ=QgiM6dShGuQB4es7qRtSjuKaQ@mail.gmail.com>
On Fri, Jul 22, 2022 at 12:43:27PM +0200, Haris Iqbal wrote:
> IMHO, in addition to finding a use case for this, another question
> would be, whether putting this restriction of "rxe_map_mr_sg" needed
> for every reg_fast_mr/invalidate_mr() cycle makes sense in terms of
> spec and/or mlx drivers.
It doesn't really, the mapping of the MR is supposed to be permanent,
the only thing invalidate does is block use of the mkey. revalidating
without remapping shouldn't be impossible.
Jason
next prev parent reply other threads:[~2022-07-22 15:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 10:29 [RESEND RFC PATCH for-next] Revert "RDMA/rxe: Create duplicate mapping tables for FMRs" Li Zhijian
2022-07-20 10:50 ` Haris Iqbal
2022-07-21 18:18 ` Bob Pearson
2022-07-25 4:00 ` lizhijian
2022-07-25 19:15 ` Bob Pearson
2022-07-21 22:19 ` Bob Pearson
2022-07-22 10:43 ` Haris Iqbal
2022-07-22 15:13 ` Jason Gunthorpe [this message]
2022-07-25 1:13 ` lizhijian
2022-07-25 2:16 ` Guoqing Jiang
2022-07-25 9:25 ` lizhijian
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=20220722151343.GA55077@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=guoqing.jiang@linux.dev \
--cc=haris.iqbal@ionos.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=rpearsonhpe@gmail.com \
--cc=yanjun.zhu@linux.dev \
/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.