From: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
To: Christopher Lameter <cl-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org>
Cc: Alex Rosenbaum
<rosenbaumalex-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Yishai Hadas <yishaih-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
"Guy Levi(SW)" <guyle-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
Leon Romanovsky <leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
"Alex @ Mellanox" <alexr-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH RFC] Introduce verbs API for multi-packet work request
Date: Fri, 15 Dec 2017 10:37:29 -0700 [thread overview]
Message-ID: <20171215173729.GC12434@ziepe.ca> (raw)
In-Reply-To: <alpine.DEB.2.20.1712140920090.6249@nuc-kabylake>
On Thu, Dec 14, 2017 at 09:21:24AM -0600, Christopher Lameter wrote:
> On Tue, 12 Dec 2017, Alex Rosenbaum wrote:
>
> > This RFC patch introduces a libibverbs API for receiving multiple packets
> > on a single work request (aka: "MP WR").
>
> So this may work like a striding rq if we set the alignment to a word or
> so?
Mellanox hardware will implement this feature using what is called
striding rq.
The samantics here have been generalized, please look if it is useful
for you..
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-12-15 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 21:15 [PATCH RFC] Introduce verbs API for multi-packet work request Alex Rosenbaum
[not found] ` <CAFgAxU-rJb6mvH_XRt0S5_-wKwv3rOnweiLJ8WSuc=9F+P0BrQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-14 15:21 ` Christopher Lameter
2017-12-15 17:37 ` Jason Gunthorpe [this message]
[not found] ` <20171215173729.GC12434-uk2M96/98Pc@public.gmane.org>
2017-12-16 14:32 ` Christopher Lameter
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=20171215173729.GC12434@ziepe.ca \
--to=jgg-uk2m96/98pc@public.gmane.org \
--cc=alexr-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=cl-vYTEC60ixJUAvxtiuMwx3w@public.gmane.org \
--cc=guyle-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=leonro-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rosenbaumalex-Re5JQEeQqe8AvxtiuMwx3w@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