All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 0/2] netfilter: nf_tables: set selection
Date: Mon, 14 Apr 2014 10:55:57 +0200	[thread overview]
Message-ID: <20140414085557.GA6346@localhost> (raw)
In-Reply-To: <20140414085235.GA6181@macbook.localnet>

On Mon, Apr 14, 2014 at 10:52:36AM +0200, Patrick McHardy wrote:
> On Mon, Apr 14, 2014 at 10:28:00AM +0200, Pablo Neira Ayuso wrote:
> > On Mon, Apr 14, 2014 at 07:56:07AM +0200, Patrick McHardy wrote:
> > > On Mon, Mar 31, 2014 at 01:53:33PM +0200, Pablo Neira Ayuso wrote:
> > > > On Fri, Mar 28, 2014 at 10:19:46AM +0000, Patrick McHardy wrote:
> > > > > These patches implement the basic set selection mechanism based on data
> > > > > characteristics provided by userspace. So far we only need to know the
> > > > > maximum number of elements.
> > > > > 
> > > > > Instead of trying to anticipate the information future set types will
> > > > > need, the plan is to add more as we require it under the assumption
> > > > > that we will converge to a state where a new set type already has
> > > > > all information required available. The expectation is that most set
> > > > > types will require the same information for estimation since they
> > > > > most likely will be some type of tree or trie.
> > > > 
> > > > I'm going to include this in the next batch for net-next before merge
> > > > window closes, which should happen soon. Thanks a lot Patrick.
> > > 
> > > I can't find neither this series, nor the patch
> > > "netfilter: nf_tables: handle more than 8 * PAGE_SIZE set name allocations"
> > > anywhere in your trees or upstream.
> > 
> > That one I missed, I'll enqueue it to the nftables tree.
> > 
> > > Am I missing something?
> > 
> > http://git.kernel.org/cgit/linux/kernel/git/pablo/nftables.git/log/
> 
> I see. I thought that tree was retired and things moved to nf/nf-next?

I already mentioned here:

http://marc.info/?l=netfilter-devel&m=139634116115356&w=2

net-next / nf-next is closed at this moment. So I kept the nftables
kernel tree open to collect things until net-next opens back not to
mix with other non-nftables things.

      reply	other threads:[~2014-04-14  8:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28 10:19 [PATCH 0/2] netfilter: nf_tables: set selection Patrick McHardy
2014-03-28 10:19 ` [PATCH 1/2] netfilter: nf_tables: implement proper " Patrick McHardy
2014-03-28 10:19 ` [PATCH 2/2] netfilter: nft_hash: use set global element counter instead of private one Patrick McHardy
2014-03-31 11:53 ` [PATCH 0/2] netfilter: nf_tables: set selection Pablo Neira Ayuso
2014-04-14  5:56   ` Patrick McHardy
2014-04-14  8:28     ` Pablo Neira Ayuso
2014-04-14  8:52       ` Patrick McHardy
2014-04-14  8:55         ` 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=20140414085557.GA6346@localhost \
    --to=pablo@netfilter.org \
    --cc=kaber@trash.net \
    --cc=netfilter-devel@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 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.