On Wed, 2016-09-21 at 22:21 +0300, Or Gerlitz wrote:
> On Wed, Sep 21, 2016 at 7:59 PM, Samudrala, Sridhar
> wrote:
> > On 9/21/2016 12:04 AM, Or Gerlitz wrote:
>
>
> >> so what happens after this patchset is applied and before the future
> work is
> >> submitted?
On Wed, Sep 21, 2016 at 7:59 PM, Samudrala, Sridhar
wrote:
> On 9/21/2016 12:04 AM, Or Gerlitz wrote:
>> so what happens after this patchset is applied and before the future work is
>> submitted? RX/TX slow path through the VFPRs isn't supported and what
>> about
On 9/21/2016 12:04 AM, Or Gerlitz wrote:
On Wed, Sep 21, 2016 at 8:45 AM, Samudrala, Sridhar
wrote:
On 9/20/2016 9:22 PM, Or Gerlitz wrote:
On Wed, Sep 21, 2016 at 6:43 AM, Jeff Kirsher
wrote:
From: Sridhar Samudrala
On Wed, Sep 21, 2016 at 8:45 AM, Samudrala, Sridhar
wrote:
> On 9/20/2016 9:22 PM, Or Gerlitz wrote:
>> On Wed, Sep 21, 2016 at 6:43 AM, Jeff Kirsher
>> wrote:
>>>
>>> From: Sridhar Samudrala
>>> This patch
On 9/20/2016 9:22 PM, Or Gerlitz wrote:
On Wed, Sep 21, 2016 at 6:43 AM, Jeff Kirsher
wrote:
From: Sridhar Samudrala
This patch enables creation of a VF Port representor/Control netdev
associated with each VF. These netdevs can be
On Wed, Sep 21, 2016 at 6:43 AM, Jeff Kirsher
wrote:
> From: Sridhar Samudrala
> This patch enables creation of a VF Port representor/Control netdev
> associated with each VF. These netdevs can be used to control and configure
> VFs from
From: Sridhar Samudrala
This patch enables creation of a VF Port representor/Control netdev
associated with each VF. These netdevs can be used to control and configure
VFs from PFs namespace. They enable exposing VF statistics, configuring
link state, mtu, fdb/vlan