On Mon, Mar 13, 2017 at 09:15:32AM -0600, David Ahern wrote:
> On 3/13/17 9:01 AM, Ido Schimmel wrote:
> > On Mon, Mar 13, 2017 at 08:39:19AM -0600, David Ahern wrote:
> >> On 3/13/17 1:38 AM, Jiri Pirko wrote:
> >>> From: Ido Schimmel
> >>>
> >>> Drivers capable of offloading VRF configurations n
On 3/13/17 9:01 AM, Ido Schimmel wrote:
> On Mon, Mar 13, 2017 at 08:39:19AM -0600, David Ahern wrote:
>> On 3/13/17 1:38 AM, Jiri Pirko wrote:
>>> From: Ido Schimmel
>>>
>>> Drivers capable of offloading VRF configurations need to know the ports
>>> are enslaved to an actual VRF device and not so
On Mon, Mar 13, 2017 at 08:39:19AM -0600, David Ahern wrote:
> On 3/13/17 1:38 AM, Jiri Pirko wrote:
> > From: Ido Schimmel
> >
> > Drivers capable of offloading VRF configurations need to know the ports
> > are enslaved to an actual VRF device and not some other L3 master.
> >
> > Add a flag to
On 3/13/17 1:38 AM, Jiri Pirko wrote:
> From: Ido Schimmel
>
> Drivers capable of offloading VRF configurations need to know the ports
> are enslaved to an actual VRF device and not some other L3 master.
>
> Add a flag to indicate netdev is a VRF master and a corresponding
> helper.
>
> Signed-
From: Ido Schimmel
Drivers capable of offloading VRF configurations need to know the ports
are enslaved to an actual VRF device and not some other L3 master.
Add a flag to indicate netdev is a VRF master and a corresponding
helper.
Signed-off-by: Ido Schimmel
Signed-off-by: Jiri Pirko
---
dr
