From: "Denis V. Lunev" <den-3ImXcnM4P+0@public.gmane.org>
To: Benjamin Thery <benjamin.thery-6ktuUTfB/bM@public.gmane.org>
Cc: "Denis V. Lunev" <dlunev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org,
Linux Containers
<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
"Denis V. Lunev" <den-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH] [NETNS49] support for per/namespace routing cache cleanup
Date: Thu, 18 Oct 2007 18:51:23 +0400 [thread overview]
Message-ID: <471772EB.2060206@sw.ru> (raw)
In-Reply-To: <471708D8.3080808-6ktuUTfB/bM@public.gmane.org>
Benjamin Thery wrote:
> Denis V. Lunev wrote:
>> Daniel Lezcano wrote:
>>> Oh, by the way, I forgot something important you spotted with the list
>>> protected by the mutex.
>>>
>>> When looking at ipv6/fib_hash.c with Benjamin, we need to browse the
>>> network namespaces list for the garbage collecting, but we are in an
>>> interrupt handler, so I can not use rtnl_lock.
>> where exactly....
>
> Actually, it is in net/ipv6/ip6_fib.c, in fib6_clean_all().
>
> fib6_clean_all() is called by fib6_run_gc() handler of the
> ip6_fib_timer.
> If we don't want to have one such timer per net namespace, in
> fib6_clean_all() we have to go through all net to clean their own
> fib_table_hash (using for_each_net() protected by rtnl_lock).
after careful thinking, one timer per/namespace looks better for me :)
next prev parent reply other threads:[~2007-10-18 14:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 11:12 [PATCH] [NETNS49] support for per/namespace routing cache cleanup Denis V. Lunev
[not found] ` <20071017111215.GA29653-aPCOdVxUTlgvJsYlp49lxw@public.gmane.org>
2007-10-17 11:46 ` Daniel Lezcano
[not found] ` <4715F60F.6060304-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-10-17 12:51 ` Denis V. Lunev
[not found] ` <4716055D.4010102-3ImXcnM4P+0@public.gmane.org>
2007-10-17 13:40 ` Daniel Lezcano
[not found] ` <471610E8.8020008-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-10-17 14:10 ` Denis V. Lunev
[not found] ` <471617CA.9090901-3ImXcnM4P+0@public.gmane.org>
2007-10-17 14:46 ` Daniel Lezcano
2007-10-17 15:05 ` Daniel Lezcano
[not found] ` <471624C0.9020108-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-10-17 17:56 ` Denis V. Lunev
[not found] ` <47164CBD.3040107-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-10-17 18:50 ` Eric W. Biederman
2007-10-18 7:18 ` Benjamin Thery
[not found] ` <471708D8.3080808-6ktuUTfB/bM@public.gmane.org>
2007-10-18 9:54 ` Denis V. Lunev
2007-10-18 14:51 ` Denis V. Lunev [this message]
[not found] ` <471772EB.2060206-3ImXcnM4P+0@public.gmane.org>
2007-10-18 16:29 ` Benjamin Thery
[not found] ` <471789FD.5020802-6ktuUTfB/bM@public.gmane.org>
2007-10-18 19:01 ` Denis V. Lunev
2007-10-18 19:05 ` Denis V. Lunev
[not found] ` <4717AE7D.1060000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2007-10-19 7:39 ` Daniel Lezcano
2007-10-19 7:39 ` Daniel Lezcano
[not found] ` <47185F2C.1070404-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-10-19 8:53 ` Denis V. Lunev
[not found] ` <47187074.3090206-3ImXcnM4P+0@public.gmane.org>
2007-10-19 19:03 ` Eric W. Biederman
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=471772EB.2060206@sw.ru \
--to=den-3imxcnm4p+0@public.gmane.org \
--cc=benjamin.thery-6ktuUTfB/bM@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=den-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
--cc=dlunev-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.