From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Kevin 'ldir' Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>
Cc: "jhs@mojatatu.com" <jhs@mojatatu.com>,
"jiri@resnulli.us" <jiri@resnulli.us>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"xiyou.wangcong@gmail.com" <xiyou.wangcong@gmail.com>,
Paul Blakey <paulb@mellanox.com>, Oz Shlomo <ozsh@mellanox.com>
Subject: Re: [RFC net-next 0/1] net: sched: Introduce conntrack action
Date: Mon, 1 Apr 2019 10:14:24 -0300 [thread overview]
Message-ID: <20190401131423.GB13514@localhost.localdomain> (raw)
In-Reply-To: <20190329204438.68777-1-ldir@darbyshire-bryant.me.uk>
Hi,
On Fri, Mar 29, 2019 at 08:45:06PM +0000, 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 clashes with the work that Paul Blakey and I are
doing to integrate conntrack with tc and vice-versa.
Considering that in this patch the action is not RCU-ified, that it is
using a struct as netlink parameter and it is dealing only with the
dscp info, seems it's easier if we/you extend our code to support this
feature as well. How does that sound to you?
The RFC I had posted is VERY outdated (message-id
cover.1548285996.git.mleitner@redhat.com), please don't use it as
reference. Not sure if Paul can post a refreshed RFC already.
Thanks,
Marcelo
next prev parent reply other threads:[~2019-04-01 13:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 19:49 [RFC PATCH 0/1 net-next] net: sched: Introduce conndscp action Kevin 'ldir' Darbyshire-Bryant
2019-03-19 19:49 ` [PATCH 1/1] " Kevin 'ldir' Darbyshire-Bryant
2019-03-21 17:58 ` kbuild test robot
2019-03-22 14:09 ` [RFC PATCH 1/1 v2] " Kevin 'ldir' Darbyshire-Bryant
2019-03-22 17:39 ` Cong Wang
2019-03-22 18:26 ` Kevin 'ldir' Darbyshire-Bryant
2019-03-22 20:05 ` Cong Wang
2019-03-22 20:50 ` Kevin 'ldir' Darbyshire-Bryant
2019-03-22 21:31 ` Cong Wang
2019-03-22 22:06 ` Kevin 'ldir' Darbyshire-Bryant
2019-03-22 23:09 ` Cong Wang
2019-03-23 17:45 ` Kevin 'ldir' Darbyshire-Bryant
2019-03-25 19:17 ` Cong Wang
2019-03-27 20:32 ` Kevin 'ldir' Darbyshire-Bryant
2019-03-29 20:45 ` [RFC net-next 0/1] net: sched: Introduce conntrack action Kevin 'ldir' Darbyshire-Bryant
2019-03-29 20:45 ` [RFC net-next 1/1] " Kevin 'ldir' Darbyshire-Bryant
2019-04-01 13:14 ` Marcelo Ricardo Leitner [this message]
2019-04-01 13:54 ` [RFC net-next 0/1] " Kevin 'ldir' Darbyshire-Bryant
2019-04-01 14:22 ` Paul Blakey
2019-04-01 21:06 ` Cong Wang
2019-04-02 9:24 ` Kevin 'ldir' Darbyshire-Bryant
2019-04-03 7:47 ` Paul Blakey
2019-04-03 8:23 ` Kevin 'ldir' Darbyshire-Bryant
2019-04-03 11:56 ` Paul Blakey
2019-04-03 12:35 ` Kevin 'ldir' Darbyshire-Bryant
2019-04-09 11:33 ` [RFC net-next 0/1] net: sched: Introduce act_ctinfo action Kevin 'ldir' Darbyshire-Bryant
2019-04-09 11:33 ` [RFC net-next 1/1] " Kevin 'ldir' Darbyshire-Bryant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190401131423.GB13514@localhost.localdomain \
--to=marcelo.leitner@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=ldir@darbyshire-bryant.me.uk \
--cc=netdev@vger.kernel.org \
--cc=ozsh@mellanox.com \
--cc=paulb@mellanox.com \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).