From: Cong Wang <xiyou.wangcong@gmail.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [Patch net-next] net_sched: add network namespace support for tc actions
Date: Mon, 22 Feb 2016 15:51:51 -0800 [thread overview]
Message-ID: <CAM_iQpVBBE6aah=5YNuBt0G+5Zb7eB-O97FVaYLWLSOjAMrCMQ@mail.gmail.com> (raw)
In-Reply-To: <56CB1053.8020102@mojatatu.com>
On Mon, Feb 22, 2016 at 5:42 AM, Jamal Hadi Salim <jhs@mojatatu.com> wrote:
> I did a quick look and i am struggling with it. The patch seems largish
> The issue is that we need to do this per kernel module so the code
> churn maybe unavoidable; hinfo stored in act_ops complicates things.
> Having said that: All the pernet operations in your
> code seem to be generic, other than to accomodate for module specific
> act_ops. Is it possible to make generic pernet operations? This way
> you could do things at tcf_register_action() for all actions.
> The challenge seems to be in the xxx_net_id which appears(sorry didnt
> look closely at the namespace code) to need to be unique id per module
> and per namespace instance - otherwise i would suggest for xxx_net_id
I got some idea to reduce the duplicated code, not all but most.
> to be part of act_ops. Could we not have an #ifdef in the namespace
> core like the netfilter code does and have one level of indirection
> for everything but the namespace 0?
I believe this should be done in a separated patch if really needed.
Thanks.
prev parent reply other threads:[~2016-02-22 23:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 0:43 [Patch net-next] net_sched: add network namespace support for tc actions Cong Wang
2016-02-20 18:36 ` Daniel Borkmann
2016-02-21 0:46 ` Cong Wang
2016-02-22 13:42 ` Jamal Hadi Salim
2016-02-22 23:51 ` Cong Wang [this message]
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='CAM_iQpVBBE6aah=5YNuBt0G+5Zb7eB-O97FVaYLWLSOjAMrCMQ@mail.gmail.com' \
--to=xiyou.wangcong@gmail.com \
--cc=daniel@iogearbox.net \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
/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).