From: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
To: Shan Wei <shanwei@cn.fujitsu.com>
Cc: Patrick McHardy <kaber@trash.net>,
David Miller <davem@davemloft.net>,
Alexey Dobriyan <adobriyan@gmail.com>,
Yasuyuki KOZAKAI <yasuyuki.kozakai@toshiba.co.jp>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
netfilter-devel@vger.kernel.org, yoshfuji@linux-ipv6.org
Subject: Re: [RFC PATCH net-next 1/7 v2]IPv6:netfilter: defrag: Handle sysctls about IPv6 conntrack defragment per-netns
Date: Sat, 13 Mar 2010 22:58:54 +0900 [thread overview]
Message-ID: <4B9B9A1E.8080102@linux-ipv6.org> (raw)
In-Reply-To: <4B88BE39.6050307@cn.fujitsu.com>
Hi,
(2010/02/27 15:39), Shan Wei wrote:
> Register nf_conntrack_frag6_{timeout,high_thresh,low_thresh} sysctls per-netns.
> nf_conntrack_frag6_timeout and ip6frag_time, nf_conntrack_frag6_low_thresh and ip6frag_low_thresh,
> nf_conntrack_frag6_high_thresh and ip6frag_high_thresh, the three sets are equivalent.
> The former sysctls are just an alias for he latter ones of IPv6.
>
> More discussion about it, see http://marc.info/?l=netfilter-devel&m=126709777922959&w=2.
As I mailed in reply to [0/7], I'm not for this,
because the context (including parameters) should be kept
separated between defragmentation in core ipv6 and one in netfilter.
--yoshfuji
next prev parent reply other threads:[~2010-03-13 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 6:39 [RFC PATCH net-next 1/7 v2]IPv6:netfilter: defrag: Handle sysctls about IPv6 conntrack defragment per-netns Shan Wei
2010-03-13 13:58 ` YOSHIFUJI Hideaki [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-27 6:39 Shan Wei
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=4B9B9A1E.8080102@linux-ipv6.org \
--to=yoshfuji@linux-ipv6.org \
--cc=adobriyan@gmail.com \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=shanwei@cn.fujitsu.com \
--cc=yasuyuki.kozakai@toshiba.co.jp \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.