From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 09/15] ipv4: Cache output routes in fib_info nexthops.
Date: Wed, 18 Jul 2012 22:34:19 +0200 [thread overview]
Message-ID: <1342643659.2626.3636.camel@edumazet-glaptop> (raw)
In-Reply-To: <20120718.112404.1910372180742347127.davem@davemloft.net>
On Wed, 2012-07-18 at 11:24 -0700, David Miller wrote:
> If we have an output route that lacks nexthop exceptions, we can cache
> it in the FIB info nexthop.
>
> Such routes will have DST_HOST cleared because such routes refer to a
> family of destinations, rather than just one.
> - const struct fib_result *res,
> +static void rt_cache_route(struct fib_nh *nh, struct rtable *rt)
> +{
> + static DEFINE_SPINLOCK(fib_cache_lock);
> + struct rtable **p = &nh->nh_rth_output;
> +
> + if (*p)
> + return;
> +
> + spin_lock_bh(&fib_cache_lock);
> + if (!*p) {
> + *p = rt;
> + dst_clone(&rt->dst);
> + }
> + spin_unlock_bh(&fib_cache_lock);
> +}
> +
This probably should use cmpxchg()
static void rt_cache_route(struct fib_nh *nh, struct rtable *rt)
{
struct rtable **p = &nh->nh_rth_output;
if (*p)
return;
if (cmpxchg(p, NULL, rt) == NULL)
dst_clone(&rt->dst);
}
next prev parent reply other threads:[~2012-07-18 20:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 18:24 [PATCH 09/15] ipv4: Cache output routes in fib_info nexthops David Miller
2012-07-18 20:34 ` Eric Dumazet [this message]
2012-07-18 20:36 ` David Miller
2012-07-18 20:40 ` Eric Dumazet
2012-07-18 20:49 ` David Miller
2012-07-19 11:38 ` Steffen Klassert
2012-07-19 15:39 ` David Miller
2012-07-19 15:52 ` David Miller
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=1342643659.2626.3636.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox