From: Jason Gunthorpe <jgg@nvidia.com>
To: Bob Pearson <rpearsonhpe@gmail.com>
Cc: Zhu Yanjun <zyjzyj2000@gmail.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
Bob Pearson <rpearson@hpe.com>
Subject: Re: [PATCH for-next] RDMA/rxe: Split MEM into MR and MW
Date: Wed, 24 Mar 2021 14:07:21 -0300 [thread overview]
Message-ID: <20210324170721.GN2356281@nvidia.com> (raw)
In-Reply-To: <c7fd30e5-dfd8-cd95-3b69-ea94432953fd@gmail.com>
On Wed, Mar 24, 2021 at 11:52:19AM -0500, Bob Pearson wrote:
> >> +struct rxe_mw {
> >> + struct rxe_pool_entry pelem;
> >> + struct ib_mw ibmw;
> >> + struct rxe_qp *qp; /* type 2B only */
> >> + struct rxe_mr *mr;
> >> + spinlock_t lock;
> >> + enum rxe_mw_state state;
> >> + u32 access;
> >> + u64 addr;
> >> + u64 length;
> >> +};
> >
> > struct rxe_qp *qp; /* type 2B only */
> > struct rxe_mr *mr;
> > spinlock_t lock;
> > enum rxe_mw_state state;
> > u32 access;
> > u64 addr;
> > u64 length;
> >
> > The above member variables are not used in your commit. Why keep them
> > in this struct rxe_mw?
> >
> > Zhu Yanjun
> >
>
> There is more to come. The goal here is to implement MW and peeking ahead
> MWs need each of those fields. As soon as this change gets accepted I will start
> adding code to implement the MW verbs APIs.
The requirement is to add things when you need them, so if these are
unused here they should move to the patch that requires them
Jason
next prev parent reply other threads:[~2021-03-24 17:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 22:26 [PATCH for-next] RDMA/rxe: Split MEM into MR and MW Bob Pearson
2021-03-16 7:18 ` Zhu Yanjun
2021-03-16 15:40 ` Bob Pearson
2021-03-18 8:20 ` Zhu Yanjun
2021-03-19 2:02 ` Zhu Yanjun
2021-03-19 18:48 ` Bob Pearson
2021-03-20 3:44 ` Zhu Yanjun
2021-03-23 5:43 ` Bob Pearson
2021-03-23 7:00 ` Zhu Yanjun
2021-03-24 16:48 ` Bob Pearson
2021-03-25 7:47 ` Zhu Yanjun
2021-03-23 11:14 ` Zhu Yanjun
2021-03-24 16:52 ` Bob Pearson
2021-03-24 17:07 ` Jason Gunthorpe [this message]
2021-03-24 17:25 ` Bob Pearson
2021-03-25 7:48 ` Zhu Yanjun
2021-03-25 7:52 ` Zhu Yanjun
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=20210324170721.GN2356281@nvidia.com \
--to=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearson@hpe.com \
--cc=rpearsonhpe@gmail.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