From: Florian Westphal <fw@strlen.de>
To: Matt Bennett <Matt.Bennett@alliedtelesis.co.nz>
Cc: "netfilter-devel@vger.kernel.org" <netfilter-devel@vger.kernel.org>
Subject: Re: Extending connmark to 64 bits
Date: Thu, 19 Nov 2015 04:00:11 +0100 [thread overview]
Message-ID: <20151119030011.GA6710@breakpoint.cc> (raw)
In-Reply-To: <1447802062.16644.12.camel@mattb-dl>
Matt Bennett <Matt.Bennett@alliedtelesis.co.nz> wrote:
> Currently we have a number of router features making use of connection
> tracking. As such we now require more than the 32 bits connmark
> currently has. Our first inclination is to extend this field to 64 bits
> and update related areas of code appropriately.
>
> The major question we have is whether there is a reason this field is 32
> bits (performance reasons or other)?
Its meant to align with skb->mark.
> If it is not possible to extend this field then perhaps there are other
> options (beyond disabling some features making use of connection
> tracking)?
Have you looked at using conntrack labels?
Its a 128bit storage area.
next prev parent reply other threads:[~2015-11-19 3:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 23:14 Extending connmark to 64 bits Matt Bennett
2015-11-19 3:00 ` Florian Westphal [this message]
2015-11-19 3:35 ` Matt Bennett
2015-11-19 21:32 ` Florian Westphal
2015-11-19 22:55 ` Matt Bennett
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=20151119030011.GA6710@breakpoint.cc \
--to=fw@strlen.de \
--cc=Matt.Bennett@alliedtelesis.co.nz \
--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).