On Sat, Feb 18, 2017 at 08:38:51AM +0100, Jiri Pirko wrote:
> Fri, Feb 17, 2017 at 09:49:07AM CET, simon.hor...@netronome.com wrote:
> >Hi Jiri,
> >
> >On Thu, Feb 16, 2017 at 04:22:37PM +0100, Jiri Pirko wrote:
> >> From: Arkadi Sharshevsky
> >>
> >> The pipeline debug is used to export the pipe
Fri, Feb 17, 2017 at 09:49:07AM CET, simon.hor...@netronome.com wrote:
>Hi Jiri,
>
>On Thu, Feb 16, 2017 at 04:22:37PM +0100, Jiri Pirko wrote:
>> From: Arkadi Sharshevsky
>>
>> The pipeline debug is used to export the pipeline abstractions
>> for the main objects - tables, headers and entries. T
Hi Jiri,
On Thu, Feb 16, 2017 at 04:22:37PM +0100, Jiri Pirko wrote:
> From: Arkadi Sharshevsky
>
> The pipeline debug is used to export the pipeline abstractions
> for the main objects - tables, headers and entries. The only support for
> set is for changing the counter parameter on specific ta
On 17-02-16 07:22 AM, Jiri Pirko wrote:
> From: Arkadi Sharshevsky
>
> The pipeline debug is used to export the pipeline abstractions
> for the main objects - tables, headers and entries. The only support for
> set is for changing the counter parameter on specific table.
>
Couple quick comments
From: Arkadi Sharshevsky
The pipeline debug is used to export the pipeline abstractions
for the main objects - tables, headers and entries. The only support for
set is for changing the counter parameter on specific table.
The basic structures:
Header - can represent a real protocol header infor
