netdev
[Top] [All Lists]

Re: [PATCH/RFC] Reduce call chain length in netfilter (take 2)

To: Bart De Schuymer <bdschuym@xxxxxxxxxx>
Subject: Re: [PATCH/RFC] Reduce call chain length in netfilter (take 2)
From: "David S. Miller" <davem@xxxxxxxxxxxxx>
Date: Wed, 9 Mar 2005 20:28:37 -0800
Cc: netdev@xxxxxxxxxxx, netfilter-devel@xxxxxxxxxxxxxxxxxxx, rusty@xxxxxxxxxxxxxxx, kaber@xxxxxxxxx, snort2004@xxxxxxx, ak@xxxxxxx, bridge@xxxxxxxx, gandalf@xxxxxxxxxxxxxx, dwmw2@xxxxxxxxxxxxx, shemminger@xxxxxxxx
In-reply-to: <1108314982.4662.2.camel@xxxxxxxxxxxxxxxxxxxxx>
References: <1108314982.4662.2.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On Sun, 13 Feb 2005 18:16:21 +0100
Bart De Schuymer <bdschuym@xxxxxxxxxx> wrote:

> This is a second try to fix the long chain call lengths in netfilter.
> The difference with the previous patch is that I got rid of the extra
> argument. I somehow didn't see it could be done without using the 'int
> *ret2' argument.
> 
> A comment on the number of arguments to nf_hook_slow: I don't think the
> number of arguments should be decreased. For the bridge-nf code, f.e.,
> the indev argument does not equal (*pskb)->dev (this is an answer to a
> question of Rusty in the old thread).
> 
> A comment on the argument change of nf_hook_slow (sk_buff * to sk_buff
> **) and the bad influence on tail call optimization possibilities. From
> the discussion in the old thread it became clear that no tail call is
> generated for the current code. So, I don't see why this is a reason not
> to accept the patch. Furthermore, if gcc ever would become able of doing
> the current code with a tail call, it should be very easy to change the
> code back to the original. In the meantime, I think this patch is the
> best known solution.

I agree with your analysis of the situation and have applied your
patch, thanks for keeping this going Bart.

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [PATCH/RFC] Reduce call chain length in netfilter (take 2), David S. Miller <=