linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Lameter <cl@linux.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Leonard Crestez <lcrestez@ixiacom.com>, Tejun Heo <tj@kernel.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Sorin Dumitru <sdumitru@ixiacom.com>
Subject: Re: [RFC v2] percpu: Add a separate function to merge free areas
Date: Thu, 4 Dec 2014 15:15:27 -0600 (CST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1412041514250.14832@gentwo.org> (raw)
In-Reply-To: <20141204205202.GP29748@ZenIV.linux.org.uk>

On Thu, 4 Dec 2014, Al Viro wrote:

> ... except that somebody has not known that and took refcounts on e.g.
> vfsmounts into percpu.  With massive amounts of hilarity once docker folks
> started to test the workloads that created/destroyed those in large amounts.

Well, vfsmounts being a performance issue is a bit weird and unexpected.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2014-12-04 21:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-02 22:33 Leonard Crestez
2014-12-04 17:57 ` Tejun Heo
2014-12-04 20:10   ` Leonard Crestez
2014-12-04 20:28     ` Christoph Lameter
2014-12-04 20:45       ` Tejun Heo
2014-12-04 20:52       ` Al Viro
2014-12-04 21:15         ` Christoph Lameter [this message]
2014-12-04 21:19           ` Tejun Heo
2014-12-04 21:20             ` Christoph Lameter
2014-12-05  6:25               ` Konstantin Khlebnikov
2014-12-04 20:42     ` Tejun Heo

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=alpine.DEB.2.11.1412041514250.14832@gentwo.org \
    --to=cl@linux.com \
    --cc=lcrestez@ixiacom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sdumitru@ixiacom.com \
    --cc=tj@kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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