All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Harald Welte <laforge@netfilter.org>,
	Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH 0/10] updates for ctnetlink and conntrack core
Date: Fri, 07 Jul 2006 07:13:56 +0200	[thread overview]
Message-ID: <44ADED94.3010703@trash.net> (raw)
In-Reply-To: <44ADC2EE.905@netfilter.org>

Pablo Neira Ayuso wrote:
> Hi,
> 
> Here follows a set of patches for ctnetlink and the conntrack core API.

I'm perfectly fine with 1, 2, and 9. Still need to look at 10 in
more detail, 3 - 5 need a bit more work. As for 6 - 8, see below.

> Basically, at the time that I was working on the ctnetlink patches, I
> tried to keep in mind the idea of reducing the netlink bandwidth
> consumption following the principle of just dumping meaningful fields
> depending on the type of event.
> 
> Please let me know what you think. Thanks!

I think this is something we need to agree on in principle. I'm
not convinced that we really do save much bandwidth in the
common case, and that its worth diverging from the usual update
notifications containing full updates sent by the remaining
network stack (besides unset fields or fields containing 0).

I'll see if I can get some numbers of the actual differences
without too much effort.

  reply	other threads:[~2006-07-07  5:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-07  2:11 [PATCH 0/10] updates for ctnetlink and conntrack core Pablo Neira Ayuso
2006-07-07  5:13 ` Patrick McHardy [this message]
2006-07-07  5:58   ` Patrick McHardy
2006-07-07  6:20     ` Patrick McHardy
2006-07-07 13:46       ` Pablo Neira Ayuso
2006-07-10  4:42         ` Patrick McHardy
2006-07-13 20:01           ` Pablo Neira Ayuso
2006-07-19 16:39             ` Patrick McHardy

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=44ADED94.3010703@trash.net \
    --to=kaber@trash.net \
    --cc=laforge@netfilter.org \
    --cc=netfilter-devel@lists.netfilter.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.