> On Tue, Sep 13, 2016 at 5:23 AM, Liang, Kan wrote:
> >>
> >> Hello.
> >>
> >> On 09/12/2016 05:55 PM, kan.li...@intel.com wrote:
> >>
> >> > From: Kan Liang
> >> >
> >> > Net policy needs to know device information. Currently, it's enough
> >> > to only get irq information of rx and tx queues
On Tue, Sep 13, 2016 at 5:23 AM, Liang, Kan wrote:
>>
>> Hello.
>>
>> On 09/12/2016 05:55 PM, kan.li...@intel.com wrote:
>>
>> > From: Kan Liang
>> >
>> > Net policy needs to know device information. Currently, it's enough to
>> > only get irq information of rx and tx queues.
>> >
>> > This patch
>
> Hello.
>
> On 09/12/2016 05:55 PM, kan.li...@intel.com wrote:
>
> > From: Kan Liang
> >
> > Net policy needs to know device information. Currently, it's enough to
> > only get irq information of rx and tx queues.
> >
> > This patch introduces ndo ops to do so, not ethtool ops.
> > Because t
Hello.
On 09/12/2016 05:55 PM, kan.li...@intel.com wrote:
From: Kan Liang
Net policy needs to know device information. Currently, it's enough to
only get irq information of rx and tx queues.
This patch introduces ndo ops to do so, not ethtool ops.
Because there are already several ways to ge
From: Kan Liang
Net policy needs to know device information. Currently, it's enough to
only get irq information of rx and tx queues.
This patch introduces ndo ops to do so, not ethtool ops.
Because there are already several ways to get irq information in
userspace. It's not necessory to extend t
