From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Yishai Hadas <yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
majd-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
Alexr-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org
Subject: Re: [PATCH RFC rdma-core] Verbs: Introduce resource domain
Date: Mon, 18 Sep 2017 14:54:11 -0600 [thread overview]
Message-ID: <20170918205411.GB7059@obsidianresearch.com> (raw)
In-Reply-To: <1505648922-21346-1-git-send-email-yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
On Sun, Sep 17, 2017 at 02:48:42PM +0300, Yishai Hadas wrote:
> Resource domain represents a collection of IB resources (as of QP, CQ,
> etc.) which are accessed by an application from the same context (e.g.
> same thread) and as such can share hardware and software resources to
> allow smarter management of resources by the provider library and better
> performance.
This sounds exactly like a PD to me. Why do we need another construct?
What is wrong with a 'thread-unsafe' flag during PD creation and then
contain the shared resources in the PD?
> uint32_t raw_packet_caps; /* Use ibv_raw_packet_caps */
> + uint32_t max_resource_domains;
Even with this approach, not sure a max makes much sense, this value should
just be hashed into whatever range the provider has on a resource by
resource basis.
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:[~2017-09-18 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 11:48 [PATCH RFC rdma-core] Verbs: Introduce resource domain Yishai Hadas
[not found] ` <1505648922-21346-1-git-send-email-yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-09-18 20:54 ` Jason Gunthorpe [this message]
[not found] ` <20170918205411.GB7059-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-09-19 14:05 ` Alex Rosenbaum
[not found] ` <CAFgAxU9M0MXw371Nh2tviuQHXCJxnFLPtaAcsevigEMMWjUPhA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-21 1:41 ` Jason Gunthorpe
[not found] ` <20170921014146.GA4041-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-09-26 9:09 ` Alex Rosenbaum
[not found] ` <CAFgAxU-FPTNM99iTACmw5yeW1zyv+7g+KC2jigj4DXiervyjdA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-30 15:59 ` Jason Gunthorpe
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=20170918205411.GB7059@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=Alexr-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=majd-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=yishaih-VPRAkNaXOzVWk0Htik3J/w@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