public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Marcel Apfelbaum <marcel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Yuval Shaia <yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
	Alex Margolin <alexma-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [RFC rdma-core 2/2] verbs: Introduce non-contiguous memory registration
Date: Tue, 30 Jan 2018 08:42:00 -0700	[thread overview]
Message-ID: <20180130154200.GD21679@mellanox.com> (raw)
In-Reply-To: <12d04e1b-6024-0763-f5c5-46ca8b0823a6-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On Tue, Jan 30, 2018 at 01:35:21PM +0200, Marcel Apfelbaum wrote:
> On 29/01/2018 19:27, Jason Gunthorpe wrote:
> >On Sun, Jan 28, 2018 at 10:37:47PM +0200, Yuval Shaia wrote:
> >
> 
> Hi Jason,
> 
> >>But let's try to take it one step further, what if all my buffers are the
> >>same size, of even better, all are PAGE_SIZE. So in case of "composite"
> >>array of let's say 262144 elements i would have wasteful 262144 * 8 bytes.
> >>
> >>This problem could be solved with a bitmap to a given range where only the
> >>bits that are set composed the MR.
> >
> >You want this for the host on virtualization right?
> 
> Yes. (actually is more about us needing rather that wanting :) )
> 
> >Like we talked
> >about at plumbers?
> > > Is it really necessary to be so optimal? A list of SGLs is not good
> >enough?
> 
> It is not. We think the list would need to be limited to a single page,
> (system calls limitation? maybe we are wrong?)

The new ioctl interface isn't really limited.
This new API(s) will run over ioctl.

> By the way, doing that would only solve half of our problem.

Well, actually, only a 3rd :| The new MR would likely be 0 based, but
the VM guest doesn't know about this. So you'd need an API that can do
arbitrary based to really solve your probably. I guess all HW should
be able to do this so maybe it is OK?

> The other problem is what is happening on post-send. We don't have a
> virtually contiguous range to pass to post-send, and breaking the
> Work Request into several work requests using pages as boundaries
> will become again a problem if we want to send a big chunk (the HW
> has a rather limited max sg elements).  We can solve it by using 0
> based MRs, do you know if the current HW supports it?

I think some does.

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

  parent reply	other threads:[~2018-01-30 15:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04 17:47 [RFC rdma-core 1/2] Registering non-contiguous memory Alex Margolin
     [not found] ` <1515088046-26605-1-git-send-email-alexma-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2018-01-04 17:47   ` [RFC rdma-core 2/2] verbs: Introduce non-contiguous memory registration Alex Margolin
     [not found]     ` <1515088046-26605-2-git-send-email-alexma-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2018-01-11 12:22       ` Yuval Shaia
2018-01-11 16:44         ` Jason Gunthorpe
     [not found]           ` <20180111164455.GA1309-uk2M96/98Pc@public.gmane.org>
2018-01-22 15:59             ` Alex Margolin
     [not found]               ` <VI1PR05MB1278C4C4FF78B4B1A551252EB9EC0-79XLn2atqDMOK6E67s+DINqRiQSDpxhJvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2018-01-23 20:29                 ` Yuval Shaia
2018-01-25 12:43                   ` Alex Margolin
     [not found]                     ` <VI1PR05MB12787572593F02F05AA20DE1B9E10-79XLn2atqDMOK6E67s+DINqRiQSDpxhJvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2018-01-25 16:07                       ` Jason Gunthorpe
2018-01-28 20:37                       ` Yuval Shaia
2018-01-29 17:27                         ` Jason Gunthorpe
     [not found]                           ` <20180129172717.GW23852-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2018-01-30 11:35                             ` Marcel Apfelbaum
     [not found]                               ` <12d04e1b-6024-0763-f5c5-46ca8b0823a6-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-01-30 15:42                                 ` Jason Gunthorpe [this message]
     [not found]                                   ` <20180130154200.GD21679-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2018-01-31 12:27                                     ` Marcel Apfelbaum
     [not found]                                       ` <76b5a8cf-b3ed-c76d-6157-91fc5f6f2b35-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-01-31 18:38                                         ` Jason Gunthorpe
     [not found]                                           ` <20180131183810.GA23352-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2018-02-01 18:22                                             ` Marcel Apfelbaum
     [not found]                                               ` <dded9055-a329-9b9d-943a-7a60445e2ada-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2018-02-01 18:29                                                 ` Jason Gunthorpe
     [not found]                                                   ` <20180201182959.GN23352-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2018-02-01 18:45                                                     ` Marcel Apfelbaum
2018-01-25 13:10                   ` Alex Margolin

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=20180130154200.GD21679@mellanox.com \
    --to=jgg-vpraknaxozvwk0htik3j/w@public.gmane.org \
    --cc=alexma-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=marcel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=yuval.shaia-QHcLZuEGTsvQT0dZR+AlfA@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