Re: [PATCH RFC 0/3] intermediate representation for jit and cls_u32 conversion

2016-02-26 Thread Alexei Starovoitov
On Fri, Feb 26, 2016 at 05:19:48PM +0100, Pablo Neira Ayuso wrote: > > Good, I'm all for reaching those numbers, we can optimize the generic > IR if this ever becomes the bottleneck. The 'generic IR' got mentioned hundred times in this thread, but what was proposed is not generic. It doesn't even

Re: [PATCH RFC 0/3] intermediate representation for jit and cls_u32 conversion

2016-02-26 Thread David Miller
From: Pablo Neira Ayuso Date: Fri, 26 Feb 2016 17:19:48 +0100 > I see no reason to have as many hooks as frontends to start with. If > you find limitations with the IR that are unfixable for any of the > existing frontends in the future, then we can add direct hook as final > solution. I see no

Re: [PATCH RFC 0/3] intermediate representation for jit and cls_u32 conversion

2016-02-26 Thread David Miller
From: Pablo Neira Ayuso Date: Fri, 26 Feb 2016 12:47:14 +0100 > The frontend parser should be generic to everyone, it should be > placed in the core, so everyone will take care of improving it. Generic unfortunately means information loss and lots of wasted work. And this is one of John's point

Re: [PATCH RFC 0/3] intermediate representation for jit and cls_u32 conversion

2016-02-26 Thread John Fastabend
On 16-02-26 08:19 AM, Pablo Neira Ayuso wrote: > On Fri, Feb 26, 2016 at 07:42:25AM -0800, John Fastabend wrote: >> On 16-02-26 03:47 AM, Pablo Neira Ayuso wrote: >>> The parser on the backend is not the way to go. I would expect it >>> will not take long time until we see other people copying/pas

Re: [PATCH RFC 0/3] intermediate representation for jit and cls_u32 conversion

2016-02-26 Thread Pablo Neira Ayuso
On Fri, Feb 26, 2016 at 07:42:25AM -0800, John Fastabend wrote: > On 16-02-26 03:47 AM, Pablo Neira Ayuso wrote: > > The parser on the backend is not the way to go. I would expect it > > will not take long time until we see other people copying/pasting it > > and adapting it to their need just bec

Re: [PATCH RFC 0/3] intermediate representation for jit and cls_u32 conversion

2016-02-26 Thread John Fastabend
On 16-02-26 03:47 AM, Pablo Neira Ayuso wrote: > On Thu, Feb 25, 2016 at 10:11:36AM -0800, John Fastabend wrote: >> On 16-02-25 09:37 AM, Pablo Neira Ayuso wrote: >>> Hi, >>> >>> This patchset contains the core infrastructure for the generic >>> intermediate representation that I presented during N

Re: [PATCH RFC 0/3] intermediate representation for jit and cls_u32 conversion

2016-02-26 Thread Pablo Neira Ayuso
On Thu, Feb 25, 2016 at 10:11:36AM -0800, John Fastabend wrote: > On 16-02-25 09:37 AM, Pablo Neira Ayuso wrote: > > Hi, > > > > This patchset contains the core infrastructure for the generic > > intermediate representation that I presented during NetDev 1.1's > > nftables switchdev talk. This inc

Re: [PATCH RFC 0/3] intermediate representation for jit and cls_u32 conversion

2016-02-25 Thread John Fastabend
On 16-02-25 09:37 AM, Pablo Neira Ayuso wrote: > Hi, > > This patchset contains the core infrastructure for the generic > intermediate representation that I presented during NetDev 1.1's > nftables switchdev talk. This includes the basic infrastructure to > convert the tc cls_u32 based on John's p

[PATCH RFC 0/3] intermediate representation for jit and cls_u32 conversion

2016-02-25 Thread Pablo Neira Ayuso
Hi, This patchset contains the core infrastructure for the generic intermediate representation that I presented during NetDev 1.1's nftables switchdev talk. This includes the basic infrastructure to convert the tc cls_u32 based on John's parser. The main goals of this patchset are: * Provide an