All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <dlezcano-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
To: Pavel Emelyanov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
Cc: Linux Containers
	<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
	Benjamin Thery <benjamin.thery-6ktuUTfB/bM@public.gmane.org>,
	"Denis V. Lunev" <den-3ImXcnM4P+0@public.gmane.org>
Subject: Re: [Devel] Re: net 2.6.25
Date: Wed, 14 Nov 2007 12:05:09 +0100	[thread overview]
Message-ID: <473AD665.3010000@fr.ibm.com> (raw)
In-Reply-To: <473AD4F5.40505-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>

Pavel Emelyanov wrote:
> Daniel Lezcano wrote:
>> Denis V. Lunev wrote:
>>> Hello, guys!
>>>
>>> David has been opened net-2.6.25 tree yesterday, so we could send a new
>>> portion of NETNS there. If there are no objections, I'll send first six
>>> patches from OpenVZ GIT tomorrow, i.e. RTNL infrastructure, Packet &
>>> Unix sockets virtualization + some our /proc cleanups.
>> Did Pavel had time to look at RCU looking mechanism to replace 
>> rtnl_lock/rtnl_unlock to protect the netns list ?
> 
> Unfortunately, I had not. Andrew has released the rc2-mm1 tree, so
> I'm now trying to prepare all the patches I wanted for this mm.
> 
> I will revisit this problem, but Denis said, that the problem we're
> trying to solve with the RCU protection can be solved w/o it, no?

Yes, if we create a timer per network namespace for ipv6 garbage 
collecting, we can avoid to use a rcu, in this case.

I am doing that right now, but I am afraid we can fall into another case 
where we need to browse the network list and I thought having the RCU 
will bring more flexibility.

But, we can live without rcu and go ahead with ipv6 anyway :)

  parent reply	other threads:[~2007-11-14 11:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-14  9:35 net 2.6.25 Denis V. Lunev
     [not found] ` <473AC169.1030202-3ImXcnM4P+0@public.gmane.org>
2007-11-14  9:52   ` Eric W. Biederman
     [not found]     ` <m1ve8517dd.fsf-T1Yj925okcoyDheHMi7gv2pdwda3JcWeAL8bYrjMMd8@public.gmane.org>
2007-11-14 10:07       ` Denis V. Lunev
     [not found]         ` <473AC8C8.6070307-3ImXcnM4P+0@public.gmane.org>
2007-11-14 18:19           ` Eric W. Biederman
2007-11-14 10:31   ` Daniel Lezcano
     [not found]     ` <473ACE7F.5080007-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-11-14 10:54       ` Denis V. Lunev
     [not found]         ` <473AD3F0.1000604-3ImXcnM4P+0@public.gmane.org>
2007-11-14 16:03           ` Eric W. Biederman
2007-11-14 10:59       ` [Devel] " Pavel Emelyanov
     [not found]         ` <473AD4F5.40505-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-11-14 11:05           ` Daniel Lezcano [this message]
2007-11-15 17:15           ` Kir Kolyshkin

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=473AD665.3010000@fr.ibm.com \
    --to=dlezcano-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=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.