netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
To: netfilter-devel@vger.kernel.org
Cc: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
Subject: [nf-next/nf_tables-experiments - v2 PATCH 0/4] fixed chain name, chain rename and rule replacement
Date: Thu,  1 Nov 2012 13:38:29 +0200	[thread overview]
Message-ID: <1351769913-5851-1-git-send-email-tomasz.bursztyka@linux.intel.com> (raw)

Hi,

Here a second version of the previous patchset, now taking care of chain's name issue. The name is fixed,
same size as in iptables.

About an alternative, it could be possible to store a variable chain name in a separate allocated memory,
kept in hash table: not the chain object itself, just the name. The key would be the chain's object pointer.
At least, from execution point of view it would not affect anything since the name is necessary only for
the user. The only issue is the memory occupied by such hash table.

I was looking quickly at the linux helpers, could not find a hashtable/map api, is there any? If so, I could
try this idea of names stored like that.

Tomasz Bursztyka (4):
  nf_tables: Change chain's name to be fixed sized
  nf_tables: Add missing policy for NFTA_CHAIN_USE
  nf_tables: Add support for changing users chain's name
  nf_tables: Add support for replacing a rule by another one.

 include/linux/netfilter/nf_tables.h |  3 ++
 include/net/netfilter/nf_tables.h   |  2 +-
 net/netfilter/nf_tables_api.c       | 87 +++++++++++++++++++++++++++++++------
 3 files changed, 77 insertions(+), 15 deletions(-)

-- 
1.7.12.4


             reply	other threads:[~2012-11-01 11:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-01 11:38 Tomasz Bursztyka [this message]
2012-11-01 11:38 ` [nf-next/nf_tables-experiments - v2 PATCH 1/4] nf_tables: Change chain's name to be fixed sized Tomasz Bursztyka
2012-11-01 11:38 ` [nf-next/nf_tables-experiments - v2 PATCH 2/4] nf_tables: Add missing policy for NFTA_CHAIN_USE Tomasz Bursztyka
2012-11-01 11:38 ` [nf-next/nf_tables-experiments - v2 PATCH 3/4] nf_tables: Add support for changing users chain's name Tomasz Bursztyka
2012-11-01 11:38 ` [nf-next/nf_tables-experiments - v2 PATCH 4/4] nf_tables: Add support for replacing a rule by another one Tomasz Bursztyka
2012-11-01 15:40 ` [nf-next/nf_tables-experiments - v2 PATCH 0/4] fixed chain name, chain rename and rule replacement Pablo Neira Ayuso

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=1351769913-5851-1-git-send-email-tomasz.bursztyka@linux.intel.com \
    --to=tomasz.bursztyka@linux.intel.com \
    --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 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).