public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jack Morgenstein <jackm-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Bob Biloxi <iambobbiloxi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: mlx4 qp allocation
Date: Thu, 13 Feb 2014 15:38:59 +0200	[thread overview]
Message-ID: <20140213153859.5c41f8ee@jpm-OptiPlex-GX620> (raw)
In-Reply-To: <CANwwZzUMPvvOEWN5xA+eOiT9uA4zOG+-cDhCks4Utv+8fqao9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Thu, 13 Feb 2014 00:18:22 +0530
Bob Biloxi <iambobbiloxi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

> The VFs need to allocate the memory for Send Queue Buffer, Receive
> Queue Buffer, Completion Queue Buffer, Event Queue Buffer.
> 
> Is that right?

Yes.

> 
> Also, as the QPs, CQs etc are created by the HCA when ALLOC_RES
> command is issued, does the PF driver need to maintain anything to
> associate the QPs, CQs created by the HCA with owners(VFs) possessing
> them?

Of course. These resources must be de-allocated if, for example, the
VM running the VF crashes -- or we have a resource leak.

This also is used for security checking, to make sure that a VF does
not mess around with resources that do not "belong" to it.

-Jack

--
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-02-13 13:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-29 10:22 mlx4 qp allocation Bob Biloxi
     [not found] ` <CANwwZzUfoNB1pyyu8VC2Do3mvCBOmeam+_9CAEW-eQbVCMdHNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-11 11:31   ` Jack Morgenstein
2014-02-12 18:48     ` Bob Biloxi
     [not found]       ` <CANwwZzUMPvvOEWN5xA+eOiT9uA4zOG+-cDhCks4Utv+8fqao9g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-13 13:38         ` Jack Morgenstein [this message]
2014-02-14 18:37           ` 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=20140213153859.5c41f8ee@jpm-OptiPlex-GX620 \
    --to=jackm-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@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