All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Joakim Axelsson <gozem@gozem.se>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: ipt_LOG and friends. Question
Date: Thu, 24 Aug 2006 18:14:53 +0200	[thread overview]
Message-ID: <44EDD07D.1020805@trash.net> (raw)
In-Reply-To: <20060824151923.GK31235@kriss.csbnet.se>

Joakim Axelsson wrote:
> The default 29-32 chars as a prefix is far too little for me. Needs to
> change to 128. But again i see some code allocating this on the stack. It
> this a problem?

We can't change it due to binary compatibility. In your local tree you
can simply increase both sizes (not on the stack of course).

> The code says that a maximum of 830 chars can be used (ICMP-pcaket with
> one recursion level).

Are you sure? That sounds a bit high.

> 128 char prefix and some more on IN, OUT, PHYSIN/OUT
> and MAC fields will give an overall figure of around 1024 chars a good
> buffer length. Anything above that can probably be cut. It won't happen
> alot.
> 
> Another idea of not allocating on the stack nor using GFP_ATOMIC is to have
> a global buffer per CPU. Is this a good idea with the hot adding and
> removing of CPUs? Are linux kernel guarantied to continue on the same CPU if
> an interupt occurs and so on? 

That seems overkill, one global buffer protected by a lock will do fine.

  reply	other threads:[~2006-08-24 16:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-24 14:03 ipt_LOG and friends. Question Joakim Axelsson
2006-08-24 15:19 ` Joakim Axelsson
2006-08-24 16:14   ` Patrick McHardy [this message]
2006-08-27 15:04     ` Joakim Axelsson
2006-08-28 10:57       ` Patrick McHardy
2006-08-28 12:03         ` Joakim Axelsson
2006-08-28 13:18           ` Patrick McHardy
2006-08-30 18:52             ` Joakim Axelsson
2006-08-31  2:16               ` Patrick McHardy
2006-08-24 16:11 ` 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=44EDD07D.1020805@trash.net \
    --to=kaber@trash.net \
    --cc=gozem@gozem.se \
    --cc=netfilter-devel@lists.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.