public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: ebiederm@xmission•com (Eric W. Biederman)
To: Benoit Lourdelet <blourdel@juniper•net>
Cc: Serge Hallyn <serge.hallyn@ubuntu•com>,
	Stephen Hemminger <stephen@networkplumber•org>,
	"netdev\@vger.kernel.org" <netdev@vger•kernel.org>
Subject: Re: [RFC][PATCH] iproute: Faster ip link add, set and delete
Date: Wed, 27 Mar 2013 08:11:43 -0700	[thread overview]
Message-ID: <874nfwri6o.fsf@xmission.com> (raw)
In-Reply-To: <CD78B3C3.76D3%blourdel@juniper.net> (Benoit Lourdelet's message of "Wed, 27 Mar 2013 13:37:45 +0000")

Benoit Lourdelet <blourdel@juniper•net> writes:

> Hello Serge,
>
> I am indeed using Eric patch with lxc.
>
> It solves the initial problem of slowness to start around 1600
> containers.

Good so now we just need a production ready patch for iproute.

> I am now able to start more than  2000 without having new containers
> slower and slower to start.

May I ask how large a box you are running and how complex your
containers are.  I am trying to get a feel for how common it is likely
to be to find people running thousands of containers on a single
machine.

Eric

  reply	other threads:[~2013-03-27 15:11 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22 22:23 [RFC][PATCH] iproute: Faster ip link add, set and delete Eric W. Biederman
2013-03-22 22:27 ` Stephen Hemminger
2013-03-26 11:51   ` Benoit Lourdelet
2013-03-26 12:40     ` Eric W. Biederman
2013-03-26 14:17       ` Serge Hallyn
2013-03-26 14:33       ` Serge Hallyn
2013-03-27 13:37         ` Benoit Lourdelet
2013-03-27 15:11           ` Eric W. Biederman [this message]
2013-03-27 17:47             ` Stephen Hemminger
2013-03-28  0:46               ` Eric W. Biederman
2013-03-28  3:20                 ` Serge Hallyn
2013-03-28  3:44                   ` Eric W. Biederman
2013-03-28  4:28                     ` Serge Hallyn
2013-03-28  5:00                       ` Eric W. Biederman
2013-03-28 13:36                         ` Serge Hallyn
2013-03-28 13:42                           ` Benoit Lourdelet
2013-03-28 15:04                             ` Serge Hallyn
2013-03-28 15:21                               ` Benoit Lourdelet
2013-03-28 22:20                                 ` Stephen Hemminger
2013-03-28 23:52                                   ` Eric W. Biederman
2013-03-29  0:13                                     ` Eric Dumazet
2013-03-29  0:25                                       ` Eric W. Biederman
2013-03-29  0:43                                         ` Eric Dumazet
2013-03-29  1:06                                           ` Eric W. Biederman
2013-03-29  1:10                                           ` Eric Dumazet
2013-03-29  1:29                                             ` Eric W. Biederman
2013-03-29  1:38                                               ` Eric Dumazet
2013-03-30 10:09                                     ` Benoit Lourdelet
2013-03-30 14:44                                       ` Eric Dumazet
2013-03-30 16:07                                         ` Benoit Lourdelet
2013-03-28 20:27             ` Benoit Lourdelet
2013-03-26 15:31     ` Eric Dumazet

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=874nfwri6o.fsf@xmission.com \
    --to=ebiederm@xmission$(echo .)com \
    --cc=blourdel@juniper$(echo .)net \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=serge.hallyn@ubuntu$(echo .)com \
    --cc=stephen@networkplumber$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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