Re: [RFC net-next 0/1] net: sched: Introduce conntrack action

2019-04-03 Thread Kevin 'ldir' Darbyshire-Bryant
> On 3 Apr 2019, at 12:56, Paul Blakey wrote: > > > > Kevin 'ldir' Darbyshire-Bryant wrote on 03/04/2019 11:23: >> >> >>> On 3 Apr 2019, at 08:47, Paul Blakey wrote: >>> >>> >>> >>> Kevin 'ldir' Darbyshire-Bryant wrote on 02/04/2019 12:24: Hi Cong & all, > On 1 Apr 2019,

Re: [RFC net-next 0/1] net: sched: Introduce conntrack action

2019-04-03 Thread Paul Blakey
Kevin 'ldir' Darbyshire-Bryant wrote on 03/04/2019 11:23: > > >> On 3 Apr 2019, at 08:47, Paul Blakey wrote: >> >> >> >> Kevin 'ldir' Darbyshire-Bryant wrote on 02/04/2019 12:24: >>> Hi Cong & all, >>> On 1 Apr 2019, at 22:06, Cong Wang wrote: On Mon, Apr 1, 2019 at 7:22 AM Pau

Re: [RFC net-next 0/1] net: sched: Introduce conntrack action

2019-04-03 Thread Kevin 'ldir' Darbyshire-Bryant
> On 3 Apr 2019, at 08:47, Paul Blakey wrote: > > > > Kevin 'ldir' Darbyshire-Bryant wrote on 02/04/2019 12:24: >> Hi Cong & all, >> >>> On 1 Apr 2019, at 22:06, Cong Wang wrote: >>> >>> On Mon, Apr 1, 2019 at 7:22 AM Paul Blakey wrote: >>> >> > > > Hi Kevin, > If you'd like, Yo

Re: [RFC net-next 0/1] net: sched: Introduce conntrack action

2019-04-03 Thread Paul Blakey
Kevin 'ldir' Darbyshire-Bryant wrote on 02/04/2019 12:24: > Hi Cong & all, > >> On 1 Apr 2019, at 22:06, Cong Wang wrote: >> >> On Mon, Apr 1, 2019 at 7:22 AM Paul Blakey wrote: >>> >> > >> >>> >>> This would probably be better off with the previous name act_conndscp. >> >> >> If naming is th

Re: [RFC net-next 0/1] net: sched: Introduce conntrack action

2019-04-02 Thread Kevin 'ldir' Darbyshire-Bryant
Hi Cong & all, > On 1 Apr 2019, at 22:06, Cong Wang wrote: > > On Mon, Apr 1, 2019 at 7:22 AM Paul Blakey wrote: >> > > >> >> This would probably be better off with the previous name act_conndscp. > > > If naming is the only concern here, then it is not hard to find > a name we are all s

Re: [RFC net-next 0/1] net: sched: Introduce conntrack action

2019-04-01 Thread Cong Wang
On Mon, Apr 1, 2019 at 7:22 AM Paul Blakey wrote: > > > > > > > > >> On 1 Apr 2019, at 14:14, Marcelo Ricardo Leitner > >> wrote: > >> > >> Hi, > >> > >> On Fri, Mar 29, 2019 at 08:45:06PM +, Kevin 'ldir' Darbyshire-Bryant > >> wrote: > >>> Hi Cong, > >>> > >>> OK, so I've renamed conndscp

Re: [RFC net-next 0/1] net: sched: Introduce conntrack action

2019-04-01 Thread Paul Blakey
> > >> On 1 Apr 2019, at 14:14, Marcelo Ricardo Leitner >> wrote: >> >> Hi, >> >> On Fri, Mar 29, 2019 at 08:45:06PM +, Kevin 'ldir' Darbyshire-Bryant >> wrote: >>> Hi Cong, >>> >>> OK, so I've renamed conndscp to conntrack and hopefully this are >>> flexible enough for future conntrack-

Re: [RFC net-next 0/1] net: sched: Introduce conntrack action

2019-04-01 Thread Kevin 'ldir' Darbyshire-Bryant
> On 1 Apr 2019, at 14:14, Marcelo Ricardo Leitner > wrote: > > Hi, > > On Fri, Mar 29, 2019 at 08:45:06PM +, Kevin 'ldir' Darbyshire-Bryant > wrote: >> Hi Cong, >> >> OK, so I've renamed conndscp to conntrack and hopefully this are >> flexible enough for future conntrack->skb operation

Re: [RFC net-next 0/1] net: sched: Introduce conntrack action

2019-04-01 Thread Marcelo Ricardo Leitner
Hi, On Fri, Mar 29, 2019 at 08:45:06PM +, Kevin 'ldir' Darbyshire-Bryant wrote: > Hi Cong, > > OK, so I've renamed conndscp to conntrack and hopefully this are > flexible enough for future conntrack->skb operations to be added in the > future. How does this one fly? This work sort of clashe

[RFC net-next 0/1] net: sched: Introduce conntrack action

2019-03-29 Thread Kevin 'ldir' Darbyshire-Bryant
Hi Cong, OK, so I've renamed conndscp to conntrack and hopefully this are flexible enough for future conntrack->skb operations to be added in the future. How does this one fly? Cheers, Kevin Kevin Darbyshire-Bryant (1): net: sched: Introduce conntrack action include/net/tc_act/tc_conntrack