netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Patrick McHardy <kaber@trash.net>,
	Pablo Neira Ayuso <pablo@netfilter.org>,
	netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] [PATCH] dynamic calculation of event message size for ctnetlink
Date: Wed, 25 Mar 2009 18:22:39 +0100	[thread overview]
Message-ID: <49CA685F.9040503@trash.net> (raw)
In-Reply-To: <20090318083840.GA9679@mail.eitzenberger.org>

Holger Eitzenberger wrote:
> On Wed, Mar 18, 2009 at 05:41:43AM +0100, Patrick McHardy wrote:
> 
>>> This calculation results in no message trim if most of those attributes
>>> are present. However, assuming the worst case (no counters, no helper,
>>> no mark, no master tuple, etc.), netlink_trim() may be called. My patch
>>> calculates the exact size, so there's no trimming for any case.
>> The numbers imply that its still a net win. But its a valid point, if
>> the common case will still result in reallocations, it might make sense
>> to include the space for a few of those members optionally to make
>> sure we don't cross the 50% waste threshold.
> 
> That's a good point.
> 
> For reference these are the attributes of TCP conntrack event, I have
> marked the optional NLAs.  I don't know what the ratio is in bytes
> though.

Thanks Holger. I'm going to apply your patches since they're already
an improvement, we can do further refinement on top.

      reply	other threads:[~2009-03-25 17:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-17  9:49 [PATCH] [PATCH] dynamic calculation of event message size for ctnetlink Pablo Neira Ayuso
2009-03-17 12:03 ` Patrick McHardy
2009-03-17 12:09   ` Pablo Neira Ayuso
2009-03-17 12:14   ` Holger Eitzenberger
2009-03-17 12:16     ` Patrick McHardy
2009-03-17 22:38       ` Pablo Neira Ayuso
2009-03-18  4:41         ` Patrick McHardy
2009-03-18  8:38           ` Holger Eitzenberger
2009-03-25 17:22             ` Patrick McHardy [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=49CA685F.9040503@trash.net \
    --to=kaber@trash.net \
    --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 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).