From: Tom Goff <thomas.goff@boeing.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: PIM-SM namespace changes
Date: Mon, 1 Jun 2009 13:28:34 -0700 [thread overview]
Message-ID: <20090601202834.GA27821@boeing.com> (raw)
In-Reply-To: <20090520004344.GA10143@boeing.com>
On Tue, May 19, 2009 at 05:43:44PM -0700, Tom Goff wrote:
> > Some bugs to fix before I can apply these Tom.
> ...
> > Also we need to seriously discuss how now we unconditionally
> > register the PIM protocols. Before we had a policy of only
> > doing so conditionally, and that's a change that needs to
> > be carefully considered and discussed.
>
> Thanks for the feedback, I think the patch below includes proper error
> handling.
>
> For protocol registration I see three basic approaches for using PIM
> with namespaces:
>
> - unconditionally add PIM when multicast routing is initialized
> (maybe only ifdef CONFIG_NET_NS, otherwise preserve the current
> behavior)
>
> - keep a count of the number of namespaces that have enabled PIM and
> add/delete PIM when transitioning from/to zero
>
> - make all or some protocol registration per network namespace
>
> There are obviously tradeoffs and I would appreciate any
> comments/suggestions on alternatives that allow namespace use of
> dynamically enabled protocols.
>
[patch omitted]
Any further thoughts on handling PIM/namespace interaction?
Tom
next prev parent reply other threads:[~2009-06-01 20:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 5:24 PIM-SM namespace changes David Miller
2009-05-20 0:43 ` Tom Goff
2009-06-01 20:28 ` Tom Goff [this message]
2009-06-01 21:24 ` David Miller
2009-06-14 10:17 ` David Miller
2009-06-15 15:58 ` Pavel Emelyanov
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=20090601202834.GA27821@boeing.com \
--to=thomas.goff@boeing.com \
--cc=davem@davemloft.net \
--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).