From: Cedric Le Goater <clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
To: Pavel Emelyanov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
Cc: "Eric W. Biederman"
<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>,
"Denis V. Lunev" <den-3ImXcnM4P+0@public.gmane.org>,
Linux Containers
<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
"Denis V. Lunev" <den-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>,
Benjamin Thery <benjamin.thery-6ktuUTfB/bM@public.gmane.org>
Subject: net namespace plans for 2.6.25 (was Re: Pid namespaces problems)
Date: Thu, 08 Nov 2007 14:42:25 +0100 [thread overview]
Message-ID: <47331241.2090501@fr.ibm.com> (raw)
In-Reply-To: <47331122.3000304-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
Pavel Emelyanov wrote:
> Daniel Lezcano wrote:
>> Denis V. Lunev wrote:
>>> Daniel Lezcano wrote:
>>>
>>>> * the first one is the locking of the network namespace list by
>>>> rtnl_lock, so from the timer callback we can not browse the network
>>>> namespace list to check the age of the routes. It is a problem I would
>>>> like to talk with Denis if he has time
>>> From my point of view, the situation is clear. The timer should be
>>> per/namespace. The situation is completely different as one in IPv4.
>> We thought to make a timer per namespace for ipv6, but we are a little
>> afraid for the performances when there will be a lot of containers.
>> Anyway, we can do a timer per namespace and optimize that later. I will
>> cook a new patch to take into account that for the next week.
>
> I propose to start a new mailing thread for net namespaces discussions
> or at least change this one's subject ;)
done.
C.
next prev parent reply other threads:[~2007-11-08 13:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <472AE42F.5000602@openvz.org>
[not found] ` <472AE42F.5000602-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-11-04 4:06 ` Pid namespaces problems Eric W. Biederman
[not found] ` <m1640id57r.fsf-T1Yj925okcoyDheHMi7gv2pdwda3JcWeAL8bYrjMMd8@public.gmane.org>
2007-11-06 7:39 ` Pavel Emelyanov
[not found] ` <47301A14.9040304-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-11-06 16:28 ` Eric W. Biederman
2007-11-07 8:28 ` Cedric Le Goater
[not found] ` <4731772D.3060806-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-11-07 8:18 ` Daniel Lezcano
2007-11-07 9:00 ` Daniel Lezcano
[not found] ` <47317EA7.6030500-GANU6spQydw@public.gmane.org>
2007-11-07 16:12 ` Pavel Emelyanov
[not found] ` <4731E3DE.6000501-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-11-07 17:24 ` Daniel Lezcano
[not found] ` <4731F4BC.4000203-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-11-08 10:40 ` Pavel Emelyanov
[not found] ` <4732E7A5.6050703-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-11-08 11:07 ` Daniel Lezcano
2007-11-08 10:53 ` Denis V. Lunev
[not found] ` <4732EA8E.7080400-3ImXcnM4P+0@public.gmane.org>
2007-11-08 13:29 ` Daniel Lezcano
[not found] ` <47330F1F.4080806-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-11-08 13:37 ` Pavel Emelyanov
[not found] ` <47331122.3000304-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-11-08 13:42 ` Cedric Le Goater [this message]
[not found] ` <47331241.2090501-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-11-08 13:45 ` net namespace plans for 2.6.25 (was Re: Pid namespaces problems) Daniel Lezcano
[not found] ` <473312FD.5030609-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-11-08 13:58 ` Pavel Emelyanov
[not found] ` <473315F5.20608-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-11-08 14:08 ` Benjamin Thery
2007-11-08 14:09 ` Daniel Lezcano
[not found] ` <473318A0.7010509-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-11-09 10:14 ` Pavel Emelyanov
2007-11-08 14:05 ` Denis V. Lunev
[not found] ` <473317A2.2020307-3ImXcnM4P+0@public.gmane.org>
2007-11-08 14:00 ` Daniel Lezcano
2007-11-08 13:43 ` Pid namespaces problems Denis V. Lunev
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=47331241.2090501@fr.ibm.com \
--to=clg-nmtc/0zbporqt0dzr+alfa@public.gmane.org \
--cc=benjamin.thery-6ktuUTfB/bM@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=den-3ImXcnM4P+0@public.gmane.org \
--cc=den-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
--cc=xemul-GEFAQzZX7r8dnm+yROfE0A@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.