From: Dennis Dalessandro <dennis.dalessandro-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Moni Shoua <monis-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"Weiny, Ira" <ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
mike.marciniszyn-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Subject: Re: [RFC] RDMA verbs transport design notes
Date: Mon, 2 Nov 2015 11:34:32 -0500 [thread overview]
Message-ID: <20151102163431.GA15228@phlsvsds.ph.intel.com> (raw)
In-Reply-To: <CAG9sBKOEs_u-YVTwS=Gk2sxRCqV+Wsdh1PyNy+baf3EBSCSbTA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Mon, Nov 02, 2015 at 03:46:52PM +0200, Moni Shoua wrote:
>> get_lid()
>> Provides the LID
>>
>LID is a special case of L2 address (MAC is another special case)
>Maybe change this to het_l2()?
I'm not particularly tied to the name, we can certainly change it to
something else. I assume that's a typo and should be "get_l2()"?
>> qp_mtu()
>> Using the SL determines the MTU (this varies per VL in OPA)
>>
>Again, this is too tied to the InfiniBand protocol.
>Also, It doesn't make sense to me that a driver won't know how to
>create a QP (this is done by the rvt) but will know how to answer
>about QP mtu. Does it?
Perhaps that should have been written as "validate_mtu()", to take the user
supplied MTU and ensure that it is valid. Keep in mind that OPA can have an
MTU that varies across VLs. For those drivers which do not support this the
function basically becomes a no-op.
>> flush_qp()
>> Flush out all pending operations for a QP that have not made it the
>> wire, and wait for that flush to finish.
>Again, needs generalization
Sure, we can work on that.
>> do_send()
>> Take a fully constructed packet and place on the wire
>>
>The hardest operation of all IMO.
>Should be efficient but yet general
We are on the same page here.
>> Next steps
>> ----------
>> We will continue posting code to GitHub [2] while we field feedback. Note
>> the repo has been moved from my previous announcement [1]. I have placed it
>> under my GitHub. Once there is more significant development and folks are
>> generally happy with the design we will begin posting to this mailing list
>> (linux-rdma).
>What's the minimal progress in the rvt and the drivers before you
>think it's ready for posting to the list?
I don't think we have a hard set minimal state before we are ready to post
to the list. Let's see how things shape up over the next couple of weeks and
if we as a community like the direction of the code and think its ready to
post we can surely do so.
-Denny
--
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
prev parent reply other threads:[~2015-11-02 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 19:41 [RFC] RDMA verbs transport design notes Dennis Dalessandro
[not found] ` <20151029194129.GE26235-W4f6Xiosr+yv7QzWx2u06xL4W9x8LtSr@public.gmane.org>
2015-11-02 13:46 ` Moni Shoua
[not found] ` <CAG9sBKOEs_u-YVTwS=Gk2sxRCqV+Wsdh1PyNy+baf3EBSCSbTA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-11-02 16:34 ` Dennis Dalessandro [this message]
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=20151102163431.GA15228@phlsvsds.ph.intel.com \
--to=dennis.dalessandro-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=ira.weiny-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mike.marciniszyn-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=monis-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;
as well as URLs for NNTP newsgroup(s).