public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Bob Biloxi <iambobbiloxi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: FMR Support in multi-function environment
Date: Tue, 11 Nov 2014 08:25:59 +0200	[thread overview]
Message-ID: <5461ABF7.7050609@mellanox.com> (raw)
In-Reply-To: <CANwwZzU+QzHqjo2wc-_E36E7PQMJhuuBsVW_Ux+JVfM_a+Ydqw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 11/10/2014 4:28 PM, Bob Biloxi wrote:
> Suppose a VF driver wants to register large amount of memory using
> FMR, will it be able to do so using the mlx4 code.

no, the proprietary FMRs are not supported for mlx4 VFs, nor for mlx5 
both PF/VFs

>
> Or FMR is supported only in dedicated mode?

use the fast reg API, see for example this commit 5587856 "IB/iser: 
Introduce fast memory registration model (FRWR)" how this is done. The 
API was introduced in commit  00f7ec3 "RDMA/core: Add memory management 
extensions support"

--
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:[~2014-11-11  6:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-10 14:28 FMR Support in multi-function environment Bob Biloxi
     [not found] ` <CANwwZzU+QzHqjo2wc-_E36E7PQMJhuuBsVW_Ux+JVfM_a+Ydqw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-11-11  6:25   ` Or Gerlitz [this message]
     [not found]     ` <5461ABF7.7050609-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2014-11-11  6:54       ` Bob Biloxi
2014-11-11 10:54   ` Jack Morgenstein
2014-11-11 13:32     ` Bob Biloxi

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=5461ABF7.7050609@mellanox.com \
    --to=ogerlitz-vpraknaxozvwk0htik3j/w@public.gmane.org \
    --cc=iambobbiloxi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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