public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Ray Lee <ray-lk@madrabbit.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	renton@renton.name, linux-kernel@vger.kernel.org
Subject: Re: devpts mounts too slowly
Date: Tue, 09 Jun 2009 17:02:59 -0700	[thread overview]
Message-ID: <4A2EF833.6080300@zytor.com> (raw)
In-Reply-To: <2c0942db0906091630l1cc79647h8689e9e929ed1bba@mail.gmail.com>

Ray Lee wrote:
>>
>> akpm2:/home/akpm/xx# time mount -n -i -t devpts none /tmp/pts
>> mount -n -i -t devpts none /tmp/pts  0.00s user 0.00s system 0% cpu 0.002 total
> 
> I read the Original Post as that test being performed with 5k /dev/pts
> already mounted.

A quick script seems to confirm that the time starts creeping up as the
number of mount points increase; on my Core i7 system the 10000th mount
takes around 50 ms whereas the early instances are submillisecond, and
the increase *seems* to be O(n log n) or thereabouts -- slightly
superlinear but not a good fit for a power law.

The same thing happens with ramfs, so the problem is either in libfs or
in the VFS; I suspect the latter as I don't really think we have had a
huge reason to optimize a very large number of mounts in the past.

	-hpa

  parent reply	other threads:[~2009-06-10  0:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-03 14:28 devpts mounts too slowly Alexey Vlasov
2009-06-03 21:28 ` H. Peter Anvin
2009-06-09 23:19   ` Andrew Morton
2009-06-09 23:30     ` Ray Lee
2009-06-09 23:53       ` Andrew Morton
2009-06-10  0:07         ` H. Peter Anvin
2009-06-10 20:51         ` H. Peter Anvin
2009-06-24 20:01           ` Al Viro
2009-06-24 21:58             ` Andrew Morton
2009-06-24 23:02               ` H. Peter Anvin
2009-06-10  0:02       ` H. Peter Anvin [this message]
2009-07-06 19:52         ` Alexey Vlasov
2009-07-06 20:03           ` Alexey Vlasov
2009-07-06 21:21           ` H. Peter Anvin
2009-07-07  8:38             ` Alexey Vlasov
2009-07-07 15:37               ` H. Peter Anvin

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=4A2EF833.6080300@zytor.com \
    --to=hpa@zytor.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ray-lk@madrabbit.org \
    --cc=renton@renton.name \
    /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