From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 10/16] ipv4: Cache output routes in fib_info nexthops.
Date: Thu, 19 Jul 2012 15:13:12 -0700 (PDT) [thread overview]
Message-ID: <20120719.151312.1882340232448320251.davem@davemloft.net> (raw)
In-Reply-To: <1342735743.2626.5411.camel@edumazet-glaptop>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Fri, 20 Jul 2012 00:09:03 +0200
> If we find orig not null, what can protect another cpu from reading
> nh->nh_rth_output, then we dst_release(orig), and other cpu does the
> dst_use() too late ?
Indeed, we'd have to defer it somehow.
Actually, we might be able to fake this by using __dst_free() on it
or something similar.
But safest would be RCU, whose protection we are still using on the
read side.
Any better ideas?
next prev parent reply other threads:[~2012-07-19 22:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 21:35 [PATCH 10/16] ipv4: Cache output routes in fib_info nexthops David Miller
2012-07-19 22:09 ` Eric Dumazet
2012-07-19 22:13 ` David Miller [this message]
2012-07-19 22:19 ` Eric Dumazet
-- strict thread matches above, loose matches on Subject: below --
2012-07-20 21:26 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=20120719.151312.1882340232448320251.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).