From: "Bjørn Mork" <bjorn@mork•no>
To: Paul Stewart <pstew@chromium•org>
Cc: netdev@vger•kernel.org
Subject: Re: [PATCHv2] ipv6: Create module parameter for use_tempaddr
Date: Tue, 13 Sep 2011 20:39:24 +0200 [thread overview]
Message-ID: <87r53ks2w3.fsf@nemi.mork.no> (raw)
In-Reply-To: <20110912212011.7C65B2041D@glenhelen.mtv.corp.google.com> (Paul Stewart's message of "Wed, 31 Aug 2011 23:03:54 -0700")
Paul Stewart <pstew@chromium•org> writes:
> When ipv6 is used as a module, there is no good place to set
> the default value for use_tempaddr. Using sysctl.conf will
> set this parameter too early -- before the module is loaded.
> To solve this, create a module parameter that will set the
> default value of use_tempaddr for all devices.
How is use_tempaddr any different from the other /proc/sys/net/ipv6/*
variables? Do you want to add a module parameter for all of them?
Why can't you run sysctl with an ipv6-specific sysctl.conf at a time
fitting your boot sequence? Or load the ipv6 module before sysctl is
loads the default sysctl.conf if that is what you want? Or just set the
variables in your network configuration scripts, prior to bringing the
interfaces up?
Or do as most people do nowadays: Forget that ipv6 can be built as a
module, and just use it builtin. It's not like it can be unloaded
anyway, so building it as a module does not give you anything.
Bjørn
next prev parent reply other threads:[~2011-09-13 18:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 6:03 [PATCH] ipv6: Create module parameter for use_tempaddr Paul Stewart
2011-09-06 23:56 ` Paul Stewart
2011-09-12 16:37 ` Paul Stewart
2011-09-12 19:51 ` Brian Haley
2011-09-01 6:03 ` [PATCHv2] " Paul Stewart
2011-09-13 18:39 ` Bjørn Mork [this message]
2011-09-13 19:56 ` Paul Stewart
2011-09-13 20:04 ` David Miller
2011-09-12 21:21 ` [PATCH] " Paul Stewart
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=87r53ks2w3.fsf@nemi.mork.no \
--to=bjorn@mork$(echo .)no \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pstew@chromium$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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