From: Chris Snook <csnook@redhat.com>
To: Julius Volz <juliusv@google.com>
Cc: Simon Horman <horms@verge.net.au>,
lvs-devel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: Should we move IPVS out of net/ipv4 now?
Date: Wed, 17 Sep 2008 14:37:33 -0400 [thread overview]
Message-ID: <48D14E6D.4020407@redhat.com> (raw)
In-Reply-To: <f4845fc0809170600s28495494l128f7dd6f00e34e3@mail.gmail.com>
Julius Volz wrote:
> Since IPVS now does partial IPv6, should we finally move it from
> "net/ipv4/ipvs" to "net" or to "net/netfilter"? I posted that patch a
> long time ago, but that was before any of the actual v6 features, so
> there was probably no interest.
Whatever the netfilter people want is fine with me.
> Also, the tunables in /proc/sys/net/ipv4/vs/... apply to both v4 and
> v6. Should we just duplicate them into /proc/sys/net/ipv6/vs? Or will
> people be confused that setting a value in one directory changes the
> value in the other and affects both IP versions?
If we do any duplication of sysctl tunables under net.ipv4 into net.ipv6, we
need to follow the same policy for all of them. Since the tcp tunables in
net.ipv4 are among the most documented and used, and have been for a decade, we
need to be conservative with that. Having two different writable tunables for
the same variable is certain to confuse. Having read-only aliases under
net.ipv6 wouldn't terrify me, but the last time I went to do tcp tuning, and saw
that the tunables in net.ipv4 weren't duplicated under net.ipv6, it was obvious
what was going on at first glance, without needing to do an ls -l to figure out
what was going on. People who prefer to use sysctl rather than manually
tweaking pseudofiles might not notice the permissions right away. By the
principle of least confusion, I think omitting them entirely is probably the way
to go.
-- Chris
next prev parent reply other threads:[~2008-09-17 18:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 13:00 Should we move IPVS out of net/ipv4 now? Julius Volz
2008-09-17 18:37 ` Chris Snook [this message]
2008-09-17 20:14 ` David Miller
2008-09-18 20:04 ` Julius Volz
2008-09-18 23:52 ` Simon Horman
2008-09-19 0:00 ` David Miller
2008-09-19 9:47 ` Julius Volz
2008-09-19 19:45 ` David Miller
2008-09-22 9:16 ` Julius Volz
2008-09-18 4:24 ` Simon Horman
2008-09-18 20:05 ` Julius Volz
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=48D14E6D.4020407@redhat.com \
--to=csnook@redhat.com \
--cc=horms@verge.net.au \
--cc=juliusv@google.com \
--cc=lvs-devel@vger.kernel.org \
--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).