this is the submit of the patch discussed yesterday to compile the sit
driver as a seperate module.
changes to yesterday:
- default select changed to y in Kconfig
- added ifdefs to net/ipv6/addrconf.c
(this part is big, to keep the patches around 100 lines the
addrconf.c changes are posted in a seperate patch)
Signed-off-by: Joerg Roedel <[email protected]>
Samuel Tardieu schrieb:
>>>>>> "Joerg" == Joerg Roedel <[email protected]> writes:
>
> Joerg> this is the submit of the patch discussed yesterday to compile
> Joerg> the sit driver as a seperate module.
>
> Your patch looks ok to me, but given that many people won't need sit,
> why is it enabled by default? Omitting it would save 10k of kernel
> text on x86 and people will see the new kernel configuration option
> anyway and will enable it if needed.
At least if set to "n" don't forget to alert the distributors (Red Hat,
etc.) to renable this. Otherwise, many clients which using 6to4 will fail...
Just my 2 cents,
Peter
--
Dr. Peter Bieringer http://www.bieringer.de/pb/
GPG/PGP Key 0x958F422D mailto:[email protected]
Deep Space 6 Co-Founder and Core Member http://www.deepspace6.net/
OpenBC http://www.openbc.com/hp/Peter_Bieringer/
Personal invitation to OpenBC http://www.openbc.com/go/invita/3889
>>>>> "Joerg" == Joerg Roedel <[email protected]> writes:
Joerg> this is the submit of the patch discussed yesterday to compile
Joerg> the sit driver as a seperate module.
Your patch looks ok to me, but given that many people won't need sit,
why is it enabled by default? Omitting it would save 10k of kernel
text on x86 and people will see the new kernel configuration option
anyway and will enable it if needed.
Sam
--
Samuel Tardieu -- [email protected] -- http://www.rfc1149.net/
On Fri, Oct 06, 2006 at 01:38:24PM +0200, Samuel Tardieu wrote:
> >>>>> "Joerg" == Joerg Roedel <[email protected]> writes:
>
> Joerg> this is the submit of the patch discussed yesterday to compile
> Joerg> the sit driver as a seperate module.
>
> Your patch looks ok to me, but given that many people won't need sit,
> why is it enabled by default? Omitting it would save 10k of kernel
> text on x86 and people will see the new kernel configuration option
> anyway and will enable it if needed.
It is enabled per default because the users get this per default when
using the current IPv6 module. James Morris mentioned this issue
yesterday. I think setting the default to N would be more consistent,
but the Y is probably less painfull for the users.
Joerg
>>>>> "Joerg" == Joerg Roedel <[email protected]> writes:
Joerg> It is enabled per default because the users get this per
Joerg> default when using the current IPv6 module. James Morris
Joerg> mentioned this issue yesterday. I think setting the default to
Joerg> N would be more consistent, but the Y is probably less painfull
Joerg> for the users.
Makes sense. I proposed this because I reconfigure my kernel with
"make oldconfig" and see new questions pop up. Maybe menuconfig and
xconfig should proeminently highlight NEW questions from the top-level
(by using a bold font on any item which is either new or has new
sub-items) so that users get a clear view of what they may need to
configure.
Sam
--
Samuel Tardieu -- [email protected] -- http://www.rfc1149.net/
In article <[email protected]> (at Fri, 6 Oct 2006 11:34:02 +0200), Joerg Roedel <[email protected]> says:
> this is the submit of the patch discussed yesterday to compile the sit
> driver as a seperate module.
>
> changes to yesterday:
> - default select changed to y in Kconfig
> - added ifdefs to net/ipv6/addrconf.c
> (this part is big, to keep the patches around 100 lines the
> addrconf.c changes are posted in a seperate patch)
>
> Signed-off-by: Joerg Roedel <[email protected]>
> + into IPv4 packets. This is usefull if you want to connect two IPv6
~~~~~~~useful
Otherwise, it seems okay to me.
--yoshfuji
On Fri, Oct 06, 2006 at 09:59:35PM +0900, YOSHIFUJI Hideaki / ?$B5HF#1QL@ wrote:
> > + into IPv4 packets. This is usefull if you want to connect two IPv6
Argh. Bad typo. I appended the fixed patch
Signed-off-by: Joerg Roedel <[email protected]>
On Fri, 6 Oct 2006 17:15:56 +0200, Joerg Roedel wrote:
> +config IPV6_SIT
> + tristate "IPv6: IPv6-in-IPv4 tunnel (SIT driver)"
> + depends on IPV6
> + default y
> + ---help---
> + Tunneling means encapsulating data of one protocol type within
> + another protocol and sending it over a channel that understands the
> + encapsulating protocol. This driver implements encapsulation of IPv6
> + into IPv4 packets. This is useful if you want to connect two IPv6
> + networks over an IPv4-only path.
> +
> + Saying M here will produce a module called sit.ko. If unsure, say N.
>From a user perspective, I believe it should say "If unsure, say Y".
The unsure case for the unsure user should be the case that works for
the broadest possible usage spectrum, which would be the 'Y' case.
To put it another way, if you pick 'Y' and don't really need it, the
only downside is wasting some memory. But if you pick 'N' and actually
did need it, previously working IPv6 networking would no longer work.
I believe the default setting should match the unsure recommendation.
-Bill
On Sat, 7 Oct 2006, Bill Fink wrote:
> On Fri, 6 Oct 2006 17:15:56 +0200, Joerg Roedel wrote:
>
> > +config IPV6_SIT
> > + tristate "IPv6: IPv6-in-IPv4 tunnel (SIT driver)"
> > + depends on IPV6
> > + default y
> > + ---help---
> > + Tunneling means encapsulating data of one protocol type within
> > + another protocol and sending it over a channel that understands the
> > + encapsulating protocol. This driver implements encapsulation of IPv6
> > + into IPv4 packets. This is useful if you want to connect two IPv6
> > + networks over an IPv4-only path.
> > +
> > + Saying M here will produce a module called sit.ko. If unsure, say N.
>
> >From a user perspective, I believe it should say "If unsure, say Y".
> The unsure case for the unsure user should be the case that works for
> the broadest possible usage spectrum, which would be the 'Y' case.
> To put it another way, if you pick 'Y' and don't really need it, the
> only downside is wasting some memory. But if you pick 'N' and actually
> did need it, previously working IPv6 networking would no longer work.
> I believe the default setting should match the unsure recommendation.
Yes, the unsure value should match the default. People pick the default
because they're unsure.
--
James Morris
<[email protected]>