[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y1wU87P4iQBF0o4z@nvidia.com>
Date: Fri, 28 Oct 2022 14:44:19 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Li Zhijian <lizhijian@...itsu.com>
Cc: Bob Pearson <rpearsonhpe@...il.com>,
Leon Romanovsky <leon@...nel.org>, linux-rdma@...r.kernel.org,
Zhu Yanjun <zyjzyj2000@...il.com>, yangx.jy@...itsu.com,
y-goto@...itsu.com, mbloch@...dia.com, liangwenpeng@...wei.com,
tom@...pey.com, tomasz.gromadzki@...el.com,
dan.j.williams@...el.com, linux-kernel@...r.kernel.org
Subject: Re: [for-next PATCH v5 00/11] RDMA/rxe: Add RDMA FLUSH operation
On Tue, Sep 27, 2022 at 01:53:26PM +0800, Li Zhijian wrote:
> Hey folks,
>
> Firstly i want to say thank you to all you guys, especially Bob, who in the
> past 1+ month, gave me a lots of idea and inspiration.
>
> With the your help, some changes are make in 5th version, such as:
> - new names and new patch split schemem, suggested by Bob
> - bugfix: set is_pmem true only if the whole MR is pmem. it's possible the
> one MR container both PMEM and DRAM.
> - introduce feth structure, instead of u32
> - new bugfix to rxe_lookup_mw() and lookup_mr(), see (RDMA/rxe: make sure requested access is a subset of {mr,mw}->access),
> with this fix, we remove check_placement_type(), lookup_mr() has done the such check.
> - Enable QP attr flushable
> These change logs also appear in the patch it belongs to.
>
> These patches are going to implement a *NEW* RDMA opcode "RDMA FLUSH".
> In IB SPEC 1.5[1], 2 new opcodes, ATOMIC WRITE and RDMA FLUSH were
> added in the MEMORY PLACEMENT EXTENSIONS section.
This doesn't apply anymore, I did try to fix it, but it ended up not
compiling, so it is better if you handle it and repost.
Thanks,
Jason
Powered by blists - more mailing lists