All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira <pablo@eurodev.net>
To: Harald Welte <laforge@netfilter.org>
Cc: Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>,
	Patrick McHardy <kaber@trash.net>
Subject: Re: [RFC] Event Cache per-cpu
Date: Wed, 10 Nov 2004 18:43:58 +0100	[thread overview]
Message-ID: <4192535E.6090409@eurodev.net> (raw)
In-Reply-To: <20041109171319.GG22257@sunbeam.de.gnumonks.org>

Harald Welte wrote:

>On Mon, Nov 08, 2004 at 08:29:38PM +0100, Pablo Neira wrote:
>  
>
>>Hi all,
>>c) per packet cache. I don't see any possible race with this approach at 
>>the moment, but I'll need to use the nfcache field in skbuff. I prefer 
>>this than adding a new field to a skbuff, I think that Davem won't like 
>>that.
>>    
>>
>
>seems fine to me.
>  
>

tony the tiger says grrrreat :)

>>There's 15 bits in nfcache available now (because IPVS guys are using 
>>one in private). My last patch has 11 events.
>>    
>>
>
>who authorized IPVS people to use that bit ? It's ours, and we fought
>hard for it  ;)  [just kidding, but I didn't know that before].
>  
>

I'll sync this between IPVS and netfilter. Make them move that to 
netfilter.h if they really need it. We'll see, later.

>>enum ip_conntrack_events
>>{
>>      IPCT_NEW,                       /* New conntrack                */
>>      IPCT_RELATED,                   /* Expected connection          */
>>      IPCT_DESTROY,                   /* Destroyed conntrack          */
>>      IPCT_STATUS,                    /* Status has changed           */
>>      IPCT_REFRESH,                   /* Timer has been refreshed     */
>>      IPCT_PROTOINFO,                 /* Update of protocol info      */
>>      IPCT_PROTOINFO_VOLATILE,        /* Volatile protocol info       */
>>      IPCT_HELPER,                    /* New helper for conntrack     */
>>      IPCT_HELPINFO,                  /* Update of helper info        */
>>      IPCT_HELPINFO_VOLATILE,         /* Volatile helper info         */
>>      IPCT_NATINFO,                   /* NAT info                     */
>>};
>>
>>Patrick suggests that we could run out of bits soon if events go in 
>>nfcache, that's true. To fix that, could we remove this stuff in 
>>netfilter_ipv4.h, nobody is using it ?
>>    
>>
>
>No, I think this can be removed, nobody has ever used nfcache the way it
>was originally intended.
>  
>

Ok, expect a new patch in next days.

Pablo

      reply	other threads:[~2004-11-10 17:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08 19:29 [RFC] Event Cache per-cpu Pablo Neira
2004-11-09 17:13 ` Harald Welte
2004-11-10 17:43   ` Pablo Neira [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=4192535E.6090409@eurodev.net \
    --to=pablo@eurodev.net \
    --cc=kaber@trash.net \
    --cc=laforge@netfilter.org \
    --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.