public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Sagi Grimberg <sagi-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
Cc: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH rdma-next 0/2] Introduce Multi-Packet receive work queue
Date: Thu, 19 Oct 2017 08:06:56 +0300	[thread overview]
Message-ID: <20171019050656.GU2106@mtr-leonro.local> (raw)
In-Reply-To: <090b4257-daf4-4f90-555c-b048764d1cda-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1784 bytes --]

On Wed, Oct 18, 2017 at 12:55:21PM +0300, Sagi Grimberg wrote:
>
> > A Multi-Packet receive WQ comes to improve performance and memory
> > footprint. It is comprised of work requests that can be consumed by
> > multiple packets. Buffers pointed by SGEs of each work request in a
> > multi packet WQ are divided into strides. Both buffer size and stride
> > size must be identical in all work requests of the same multi packet
> > WQ and are set during WQ creation.
> >
> > A single WR in a Multi-Packet WQ can generate multiple completions,
> > depends on the number of packets consumed. Each packet starts at the
> > beginning of a stride and is written in stride granularity.
> >
> > Here is an example of a work request comprised of 3 strides. Packet 1
> > is larger than a stride so it occupies 2 strides. Packet 2 fits in a
> > single stride. Each packet will generate its own completion.
> >
> > |         |         |[packet2]|
> > |    [packet1]      |         |
> > |_________|_________|_________|
> >   stride      stride     stride
> >   <--      work request     -->
> >
> > A Multi-Packet WQ reduces the number of needed post-recv operations
> > thus increasing performance: In the example above, a single post-recv
> > operation was performed instead of 2.
>
> Looks like a nice feature, would be nice if we could use it... The
> problem is that adding a different logic in case this feature exists is
> messy and difficult. Is there any way we can come up with a verbs API
> that will utilize this feature but hide the implementation details from
> the ULPs?

We will be more than happy to work with the community and update our
driver's code if needed, once the community will converge on the proper API.
Right now, we are exposing it through our DV interface.

Thanks

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-10-19  5:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-17 15:01 [PATCH rdma-next 0/2] Introduce Multi-Packet receive work queue Leon Romanovsky
     [not found] ` <20171017150113.8544-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-10-17 15:01   ` [PATCH rdma-next 1/2] IB/mlx5: Expose multi-packet RQ capabilities Leon Romanovsky
2017-10-17 15:01   ` [PATCH rdma-next 2/2] IB/mlx5: Allow creation of a multi-packet RQ Leon Romanovsky
2017-10-18  9:55   ` [PATCH rdma-next 0/2] Introduce Multi-Packet receive work queue Sagi Grimberg
     [not found]     ` <090b4257-daf4-4f90-555c-b048764d1cda-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2017-10-19  5:06       ` Leon Romanovsky [this message]
2017-10-25 18:04   ` Doug Ledford

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=20171019050656.GU2106@mtr-leonro.local \
    --to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sagi-NQWnxTmZq1alnMjI0IkVqw@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