On 8/3/2012 4:40 AM, Jack Morgenstein wrote:
> 1. Introduce the basic sriov parvirtualization context objects
> for multiplexing and demultiplexing MADs.
> 2. Introduce support for the new proxy and tunnel QP types.
>
> This patch introduces the objects required by the master
> for managing QP paravirtualization for guests.
>
> struct mlx4_ib_sriov{} is created by the master only.
> It is a container for the following:
> 1. All the info required by the PPF to multiplex and de-multiplex MADs
> (including those from the PF). (struct mlx4_ib_demux_ctx demux)
OK, so can we have at least a single reference to the various
abbreviations before using them exclusively? I know PF and PPF may be
common, but it might be nice that they were used once in full form
before abbreviated in commit messages.
> 2. All the info required to manage alias GUIDs (i.e., the GUID at
> index 0 that each guest perceives. In fact, this is not the
> GUID which is actually at index 0, but is, in fact, the GUID
> which is at index[<VF number>] in the physical table.
OK, this has been one of the things that has made reviewing this
difficult. I freely admit that I've steadfastly ignored SRIOV for as
long as I can, so maybe this is just me. But, in the context of this
driver, how am I supposed to know which code paths will be on the host
and which on the guest?
Also, I note that you do math every time you want to know if you are on
a parent device or a virtual device. Do you really want to do math all
the time, or would it be better to save off your status on device init
and just refer to that when you would do math in this patch?
--
Doug Ledford <dledf...@redhat.com>
GPG KeyID: 0E572FDD
http://people.redhat.com/dledford
Infiniband specific RPMs available at
http://people.redhat.com/dledford/Infiniband
signature.asc
Description: OpenPGP digital signature
