[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1270127120.2229.93.camel@edumazet-laptop>
Date: Thu, 01 Apr 2010 15:05:20 +0200
From: Eric Dumazet <eric.dumazet@...il.com>
To: Timo Teras <timo.teras@....fi>
Cc: netdev@...r.kernel.org, Herbert Xu <herbert@...dor.apana.org.au>
Subject: Re: [PATCH 1/4] flow: virtualize flow cache entry methods
Le jeudi 01 avril 2010 à 15:52 +0300, Timo Teras a écrit :
> This allows to validate the cached object before returning it.
> It also allows to destruct object properly, if the last reference
> was held in flow cache. This is also a prepartion for caching
> bundles in the flow cache.
>
> In return for virtualizing the methods, we save on:
> - not having to regenerate the whole flow cache on policy removal:
> each flow matching a killed policy gets refreshed as the getter
> function notices it smartly.
> - we do not have to call flow_cache_flush from policy gc, since the
> flow cache now properly deletes the object if it had any references
>
> Signed-off-by: Timo Teras <timo.teras@....fi>
> ---
...
> @@ -481,6 +482,7 @@ struct xfrm_policy {
> atomic_t refcnt;
> struct timer_list timer;
>
> + struct flow_cache_entry_ops *fc_ops;
> u32 priority;
> u32 index;
> struct xfrm_mark mark;
...
> +static struct flow_cache_entry_ops xfrm_policy_fc_ops __read_mostly = {
> + .get = xfrm_policy_get_fce,
> + .check = xfrm_policy_check_fce,
> + .delete = xfrm_policy_delete_fce,
> +};
>
Any particular reason these flow_cache_entry_ops are not const ?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists