From: David Miller <davem@davemloft.net>
To: fubar@us.ibm.com
Cc: brian.haley@hp.com, arvidjaar@mail.ru, vladislav.yasevich@hp.com,
chuck.lever@oracle.com, tytso@mit.edu, Valdis.Kletnieks@vt.edu,
rjw@sisk.pl, netdev@vger.kernel.org,
bonding-devel@lists.sourceforge.net, jamagallon@ono.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] bonding: move IPv6 support into a separate kernel module
Date: Wed, 25 Feb 2009 14:14:30 -0800 (PST) [thread overview]
Message-ID: <20090225.141430.166906161.davem@davemloft.net> (raw)
In-Reply-To: <28797.1235599858@death.nxdomain.ibm.com>
From: Jay Vosburgh <fubar@us.ibm.com>
Date: Wed, 25 Feb 2009 14:10:58 -0800
> I've been fooling with the disable_ipv6 sysctl, and one issue is
> that, at least on the distro I'm testing on (SLES), it's not picked up
> from /etc/sysctl.conf at boot time (presumably because ipv6 isn't loaded
> yet, although I haven't really checked).
Correct, that's the problem.
We could create a blocker bitmap. Two sysctls, "block_af" and
"unblock_af". You write the AF_foo value for the protocol there and
it sets or clears the assosciated bit in the internal blocker bitmap.
Things like sys_socket() et al. key off of this.
next prev parent reply other threads:[~2009-02-25 22:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 20:44 Brian Haley
2009-02-25 22:10 ` Jay Vosburgh
2009-02-25 22:14 ` David Miller [this message]
2009-02-26 16:44 ` Brian Haley
2009-02-26 18:14 ` Jay Vosburgh
2009-02-26 18:38 ` Vlad Yasevich
2009-02-26 19:49 ` Jay Vosburgh
2009-02-26 19:28 ` Brian Haley
2009-02-26 19:41 ` Chuck Lever
2009-02-26 19:59 ` Vlad Yasevich
2009-02-26 20:01 ` Brian Haley
2009-02-26 20:12 ` Chuck Lever
2009-02-26 20:17 ` Vlad Yasevich
2009-02-26 20:10 ` Vlad Yasevich
2009-02-26 20:20 ` Jay Vosburgh
2009-02-26 20:57 ` Vlad Yasevich
2009-02-26 21:56 ` Jay Vosburgh
2009-02-27 7:25 ` Kyle Moffett
2009-02-27 7:34 ` David Miller
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=20090225.141430.166906161.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Valdis.Kletnieks@vt.edu \
--cc=arvidjaar@mail.ru \
--cc=bonding-devel@lists.sourceforge.net \
--cc=brian.haley@hp.com \
--cc=chuck.lever@oracle.com \
--cc=fubar@us.ibm.com \
--cc=jamagallon@ono.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tytso@mit.edu \
--cc=vladislav.yasevich@hp.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
Powered by JetHome