All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Graf <tgraf@suug.ch>
To: Patrick McHardy <kaber@trash.net>
Cc: pablo@netfilter.org, davem@davemloft.net,
	herbert@gondor.apana.org.au, netfilter-devel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH 1/2] rhashtable: provide len to obj_hashfn
Date: Sun, 22 Mar 2015 10:39:51 +0000	[thread overview]
Message-ID: <20150322103951.GA1185@casper.infradead.org> (raw)
In-Reply-To: <1426952290-18962-2-git-send-email-kaber@trash.net>

On 03/21/15 at 03:38pm, Patrick McHardy wrote:
> nftables sets will be converted to use so called setextensions, moving
> the key to a non-fixed position. To hash it, the obj_hashfn must be used,
> however it so far doesn't receive the length parameter.
> 
> Pass the key length to obj_hashfn() and convert existing users.
> 
> Signed-off-by: Patrick McHardy <kaber@trash.net>

Acked-by: Thomas Graf <tgraf@suug.ch>

  parent reply	other threads:[~2015-03-22 10:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-21 15:38 [PATCH 0/2] netfilter: preparatory patches for set extensions Patrick McHardy
2015-03-21 15:38 ` [PATCH 1/2] rhashtable: provide len to obj_hashfn Patrick McHardy
2015-03-21 23:06   ` Herbert Xu
2015-03-22  4:47     ` Patrick McHardy
2015-03-22  7:22       ` Herbert Xu
2015-03-22  7:31         ` Patrick McHardy
2015-03-22 10:39   ` Thomas Graf [this message]
2015-03-21 15:38 ` [PATCH 2/2] netfilter: nft_hash: convert to use rhashtable callbacks Patrick McHardy
2015-03-21 23:04 ` [PATCH 0/2] netfilter: preparatory patches for set extensions Herbert Xu
2015-03-22  4:48   ` Patrick McHardy
2015-03-23 20:44 ` 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=20150322103951.GA1185@casper.infradead.org \
    --to=tgraf@suug.ch \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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.