From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
Cc: sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
roid-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH RFC] RDMA/core: add rdma_get_dma_mr()
Date: Thu, 25 Jun 2015 15:39:44 -0600 [thread overview]
Message-ID: <20150625213944.GA27780@obsidianresearch.com> (raw)
In-Reply-To: <20150625212917.14869.66238.stgit-T4OLL4TyM9aNDNWfRnPdfg@public.gmane.org>
On Thu, Jun 25, 2015 at 04:29:17PM -0500, Steve Wise wrote:
> - * ib_dma_mapping_error - check a DMA addr for error
> + * rdma_mr_roles - possible roles a MR will be used for
> + *
> + * This allows a transport independent RDMA application to
> + * create MRs that are usable for all the desired roles w/o
> + * having to understand which access rights are needed.
> + */
> +enum rdma_mr_roles {
> + RDMA_MRR_RECV = 1,
> + RDMA_MRR_SEND = (1<<1),
> + RDMA_MRR_READ_SOURCE = (1<<2),
> + RDMA_MRR_READ_SINK = (1<<3),
> + RDMA_MRR_WRITE_SOURCE = (1<<4),
> + RDMA_MRR_WRITE_SINK = (1<<5),
> + RDMA_MRR_ATOMIC = (1<<6),
> + RDMA_MRR_MW_BIND = (1<<7),
> + RDMA_MRR_ZERO_BASED = (1<<8),
> + RDMA_MRR_ACCESS_ON_DEMAND = (1<<9),
So we don't have this problem again, it would be best to explicitly
list exactly which ib_wc_opcode members what use a RKEY are matched to
which MMR flags
RDMA_MRR_RECV
LOCAL: post to receive work queue
RDMA_MRR_READ_SOURCE
LOCAL: post IB_WC_RDMA_READ to send work queue
RDMA_MRR_READ_SINK
REMOTE: respond to IB_WC_RDMA_READ
[..]
Seems reasonable to me otherwise
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-06-25 21:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 21:29 [PATCH RFC] RDMA/core: add rdma_get_dma_mr() Steve Wise
[not found] ` <20150625212917.14869.66238.stgit-T4OLL4TyM9aNDNWfRnPdfg@public.gmane.org>
2015-06-25 21:39 ` Jason Gunthorpe [this message]
[not found] ` <20150625213944.GA27780-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2015-06-25 21:48 ` Steve Wise
2015-06-25 22:37 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A82373A8FF9ECA-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-06-26 14:02 ` Steve Wise
[not found] ` <558D5B6E.6090900-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2015-06-26 15:18 ` Steve Wise
2015-06-28 15:44 ` Haggai Eran
2015-06-28 15:47 ` Haggai Eran
[not found] ` <55901703.3050001-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-06-29 13:47 ` Steve Wise
2015-06-29 15:55 ` Jason Gunthorpe
[not found] ` <20150629155503.GA2755-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2015-06-29 16:08 ` Hefty, Sean
2015-06-28 16:01 ` Haggai Eran
[not found] ` <55901A44.8020103-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-06-29 1:31 ` Hefty, Sean
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=20150625213944.GA27780@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=roid-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=sagig-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org \
/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