netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: mkubecek@suse.cz
Cc: netdev@vger.kernel.org, kuznet@ms2.inr.ac.ru, jmorris@namei.org,
	yoshfuji@linux-ipv6.org, kaber@trash.net
Subject: Re: [PATCH net] ipv6: prevent fib6_run_gc() contention
Date: Tue, 11 Jun 2013 14:22:29 -0700 (PDT)	[thread overview]
Message-ID: <20130611.142229.497972115797274443.davem@davemloft.net> (raw)
In-Reply-To: <20130611204912.GA1255@lion.mk-sys.cz>

From: Michal Kubecek <mkubecek@suse.cz>
Date: Tue, 11 Jun 2013 22:49:12 +0200

> On Tue, Jun 11, 2013 at 01:01:14PM -0700, David Miller wrote:
>> From: Michal Kubecek <mkubecek@suse.cz>
>> Date: Tue, 11 Jun 2013 12:07:18 +0200
>> 
>> > On Mon, Jun 10, 2013 at 02:26:42PM -0700, David Miller wrote:
>> >> 
>> >> It seems to me that it would be much simpler to simply update
>> >> ip6_rt_last_gc first, that way the other threads would elide the GC
>> >> call.
>> > 
>> > That was my original idea but I was afraid that while the remaining
>> > window in ip6_dst_gc() would be very short and probably safe, we could
>> > still run into problem if fib6_gc_lock was locked by some other caller
>> > of fib6_run_gc() which doesn't update net->ipv6.ip6_rt_last_gc,
>> > especially via a timer.
>> 
>> Why don't you simply try it and find out?
> 
> I don't have the system where the issue was observed at hand. I'll have
> to ask the customer who reported it to run the test so that it may take
> some time.

Please also take care of the issue Eric mentioned, in that some GC
calls erroneously do not update the last GC timestamp.

  reply	other threads:[~2013-06-11 21:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-04 11:08 [PATCH net] ipv6: prevent fib6_run_gc() contention Michal Kubecek
2013-06-10 21:26 ` David Miller
2013-06-11 10:07   ` Michal Kubecek
2013-06-11 10:40     ` Eric Dumazet
2013-06-11 20:01     ` David Miller
2013-06-11 20:49       ` Michal Kubecek
2013-06-11 21:22         ` David Miller [this message]
2013-07-31 22:19           ` Michal Kubecek
2013-07-31 23:43             ` 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=20130611.142229.497972115797274443.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jmorris@namei.org \
    --cc=kaber@trash.net \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=mkubecek@suse.cz \
    --cc=netdev@vger.kernel.org \
    --cc=yoshfuji@linux-ipv6.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).