public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz@mellanox.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: roland@kernel.org, stable@vger.kernel.org, linux-rdma@vger.kernel.org
Subject: Re: [PATCH v3.10.y 0/4] IB/IPoIB fixes for SRIOV / cloud environment
Date: Tue, 6 Aug 2013 14:22:43 +0300	[thread overview]
Message-ID: <5200DC83.6030903@mellanox.com> (raw)
In-Reply-To: <20130806093837.GC27889@kroah.com>

On 06/08/2013 12:38, Greg KH wrote:
> On Tue, Aug 06, 2013 at 11:38:38AM +0300, Or Gerlitz wrote:
>> Hi Greg,
>>
>> This series contains few fixes to the IB core, mlx4 IB driver and IPoIB.
>>
>> The patches enable working properly with IPoIB devices set over SRIOV
>> Virtual Functions probed to VMs in cloud environment when the cloud
>> management system uses non trivial settings of IB PKEYs (Partition-Keys
>> , sort of Ethernet vlans equivalent).
> That really sounds like a new feature, and not a bugfix, for these devices, right?



Hi Greg,

well... not really

3eac103 IB/mlx4: Use default pkey when creating tunnel QPs
ef5ed41 IB/core: Create QP1 using the pkey index which contains the 
default pkey

are point bug fixes to code in the IB core and mlx4 IB driver which assumed
that the default IB Partition-Key is located in index 0 of the PKEY table,
which isn't necessarily the case in virtualization environments.

3d790a4 IPoIB: Make sure child devices use valid/proper pkeys

is bug fix to the IPoIB driver to make sure we disallow child device
creation with invalid IB PKEY

and finally

c290414 IPoIB: Fix pkey change flow for virtualization environments

is indeed a bit of heavier but is a fix, the text there saying

> IPoIB's required behaviour w.r.t to the pkey used by the device is the following:
>
> - For "parent" interfaces (e.g ib0, ib1, etc) who are created
>    automatically as a result of hot-plug events from the IB core, the
>    driver needs to take whatever pkey vlaue it finds in index 0, and
>    stick to that index.
>
> - For child interfaces (e.g ib0.8001, etc) created by admin directive,
>    the driver needs to use and stick to the value provided during its
>    creation.
>

came to describe the driver design and how it works when the bug doesn't 
trigger,
the patch itself fixes the driver to always work along this design


> I need an agreement from the IB maintainers that this really is stable
> material before I can accept it.

sure, fair enough, just wanted to shed more light on the matter.

Or.

  reply	other threads:[~2013-08-06 11:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1375778322-24408-1-git-send-email-ogerlitz@mellanox.com>
2013-08-06  9:38 ` [PATCH v3.10.y 0/4] IB/IPoIB fixes for SRIOV / cloud environment Greg KH
2013-08-06 11:22   ` Or Gerlitz [this message]
2013-08-12 10:38     ` Or Gerlitz
     [not found]       ` <5208BB43.60109-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-08-22 21:43         ` Greg KH
2013-08-22 22:36           ` Roland Dreier
2013-08-25  8:10             ` Or Gerlitz
2013-08-25 16:19               ` Greg KH
     [not found]                 ` <20130825161936.GA4808-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-08-26 11:36                   ` Or Gerlitz

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=5200DC83.6030903@mellanox.com \
    --to=ogerlitz@mellanox.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=roland@kernel.org \
    --cc=stable@vger.kernel.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