All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: stomping static data pull
Date: Thu, 29 Oct 2009 16:59:58 +0100	[thread overview]
Message-ID: <4AE9BBFE.400@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.00.0910281817210.15948@obet.zrqbmnf.qr>

Jan Engelhardt wrote:
> On Wednesday 2009-10-28 16:57, Patrick McHardy wrote:
>> Jan Engelhardt wrote:
>>> I incorporated your suggestions and propose this new 4-series set.
>> Could you give me a short description of the changes relative
>> to the first incarnation? Thanks.
> 
> http://osdir.com/ml/general/2009-08/msg10540.html
> - splitting xt_repldata_create
> - giving it a name of your choice
> - return semantics (found a missing return keyword; just refreshed top 
> is commit v2.6.32-rc3-4-g7891b6c)
> 

OK thanks, that leaves my worries about adding additional runtime
overhead. I'll do some quick benchmarks to see if it really has
a measurable impact.

  reply	other threads:[~2009-10-29 16:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-10  9:22 stomping static data pull Jan Engelhardt
2009-10-10  9:22 ` [PATCH 1/4] netfilter: xtables: compact table hook functions (1/2) Jan Engelhardt
2009-10-10  9:22 ` [PATCH 2/4] netfilter: xtables: compact table hook functions (2/2) Jan Engelhardt
2009-10-10  9:22 ` [PATCH 3/4] netfilter: xtables: use xt_table for hook instantiation Jan Engelhardt
2009-10-10  9:22 ` [PATCH 4/4] netfilter: xtables: generate initial table on-demand Jan Engelhardt
2009-10-20 15:44 ` stomping static data pull Jan Engelhardt
2009-10-23  8:51   ` Jozsef Kadlecsik
2009-10-28 15:57 ` Patrick McHardy
2009-10-28 17:37   ` Jan Engelhardt
2009-10-29 15:59     ` Patrick McHardy [this message]
2009-12-04 12:06       ` Jan Engelhardt
2009-12-04 12:11         ` Patrick McHardy
2010-02-06  1:31           ` Jan Engelhardt
2010-02-06  2:31             ` Jan Engelhardt

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=4AE9BBFE.400@trash.net \
    --to=kaber@trash.net \
    --cc=jengelh@medozas.de \
    --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.