From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH net-next 1/4] ipip: allow to deactivate the creation of fb dev
Date: Fri, 16 Nov 2012 17:46:11 +0100 [thread overview]
Message-ID: <50A66DD3.20807@6wind.com> (raw)
In-Reply-To: <20121116082926.1c6cccd2@nehalam.linuxnetplumber.net>
Le 16/11/2012 17:29, Stephen Hemminger a écrit :
> On Fri, 16 Nov 2012 17:14:13 +0100
> Nicolas Dichtel <nicolas.dichtel@6wind.com> wrote:
>
>> Now that tunnels can be configured via rtnetlink, this device is not mandatory.
>> The default is conservative.
>>
>> Signed-off-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
>
>
> Although I am in favor of reducing clutter, and we even have to put in special case
> code to ignore these stub devices in the Vyatta scripts. Module parameters are bit of a nuisance to deal with, but maybe
> the only way for this kind of thing and keep the required ABI.
>
> Not sure if I can fully endorse this. The device may still have uses.
> It is still useful for capturing "none of the above" packets
If you need to capture these packets, you can still create a tunnel with local
any and remote any, even if the fb_device has not been created.
> and is used to auto-load module via module aliases.
Right, but if user uses netlink, the problem exists without these patches too.
By default, the fb device is created, so there is no change if you don't set
explicitly setup_fb to 0.
next prev parent reply other threads:[~2012-11-16 16:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 16:14 [PATCH net-next 0/4] Allow to deactivate fb tunnels device Nicolas Dichtel
2012-11-16 16:14 ` [PATCH net-next 1/4] ipip: allow to deactivate the creation of fb dev Nicolas Dichtel
2012-11-16 16:29 ` Stephen Hemminger
2012-11-16 16:46 ` Nicolas Dichtel [this message]
2012-11-20 0:07 ` David Miller
2012-11-20 8:30 ` Nicolas Dichtel
2012-11-20 8:34 ` David Miller
2012-11-20 8:41 ` [RESEND PATCH net-next 1/1] sit: allow to configure 6rd tunnels via netlink Nicolas Dichtel
2012-11-20 17:01 ` Stephen Hemminger
2012-11-20 17:11 ` Nicolas Dichtel
2012-11-20 17:17 ` Stephen Hemminger
2012-11-20 17:22 ` Nicolas Dichtel
2012-11-20 18:45 ` David Miller
2012-11-20 0:06 ` [PATCH net-next 1/4] ipip: allow to deactivate the creation of fb dev David Miller
2012-11-16 16:14 ` [PATCH net-next 2/4] sit: allow to configure 6rd tunnels via netlink Nicolas Dichtel
2012-11-16 16:14 ` [PATCH net-next 3/4] sit: allow to deactivate the creation of fb device Nicolas Dichtel
2012-11-16 16:14 ` [PATCH net-next 4/4] ip6tnl: allow to deactivate the creation of fb dev Nicolas Dichtel
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=50A66DD3.20807@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).