From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Changli Gao <xiaosuo@gmail.com>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 0/7] [RFC] new cttimeout infrastructure
Date: Sat, 3 Mar 2012 14:40:24 +0100 [thread overview]
Message-ID: <20120303134024.GB18857@1984> (raw)
In-Reply-To: <CABa6K_GKpkAiC7ae+-OwGG_b1iXyYD9+_xzF095XGTJ+e1aBWw@mail.gmail.com>
On Thu, Mar 01, 2012 at 08:51:56PM +0800, Changli Gao wrote:
> On Wed, Feb 29, 2012 at 10:39 AM, <pablo@netfilter.org> wrote:
> > From: Pablo Neira Ayuso <pablo@netfilter.org>
> >
> > You can find the user-space library:
> >
> > http://git.netfilter.org/cgi-bin/gitweb.cgi?p=libnetfilter_cttimeout.git;a=summary
> >
>
> IMHO we have too many such libraries. Why not combine all the library
> into one named after libnf or libnetfilter?
We discussed this before. We can release independent libraries in case
of bugs.
prev parent reply other threads:[~2012-03-03 13:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 2:39 [PATCH 0/7] [RFC] new cttimeout infrastructure pablo
2012-02-29 2:39 ` [PATCH 1/7] netfilter: nf_ct_udp[lite]: convert UDP[lite] timeouts to array pablo
2012-02-29 2:39 ` [PATCH 2/7] netfilter: nf_ct_tcp: move retransmission and unacknowledged timeout " pablo
2012-02-29 2:39 ` [PATCH 3/7] netfilter: nf_ct_gre: add unsigned int array to define timeouts pablo
2012-02-29 2:39 ` [PATCH 4/7] netfilter: nf_conntrack: pass timeout array to l4->new and l4->packet pablo
2012-02-29 2:39 ` [PATCH 5/7] netfilter: add cttimeout infrastructure for fine timeout tuning pablo
2012-02-29 2:39 ` [PATCH 6/7] netfilter: nf_ct_ext: add timeout extension pablo
2012-02-29 2:39 ` [PATCH 7/7] netfilter: xt_CT: allow to attach timeout policy + glue code pablo
2012-03-01 12:51 ` [PATCH 0/7] [RFC] new cttimeout infrastructure Changli Gao
2012-03-03 13:40 ` Pablo Neira Ayuso [this message]
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=20120303134024.GB18857@1984 \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=xiaosuo@gmail.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;
as well as URLs for NNTP newsgroup(s).