All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Matthew Wilcox <willy@debian.org>,
	linux-fsdevel@vger.kernel.org, dwmw2@infradead.org
Subject: Re: simultaneous creates in a directory
Date: Fri, 27 Sep 2002 13:44:25 -0700	[thread overview]
Message-ID: <20020927204425.GT22942@holomorphy.com> (raw)
In-Reply-To: <3D94B512.2BDF1840@digeo.com>

Matthew Wilcox wrote:
>> At startup, tiobench does a large number of open(O_CREAT) calls, all
>> in the same directory.  This leads to a large number of processes all
>> trying to do down() on the parent directory's i_sem.  That wouldn't be
>> so bad, but each one is sleeping with an entire page (of ZONE_NORMAL)
>> allocated.  800MB of ZONE_NORMAL / 4k pages.. ok, it'd take 200,000
>> tasks to completely OOM your box, but a user can certainly make life
>> difficult for us with fewer tasks.
>> The most important question is: Do we care?  tiobench is only a benchmark.

On Fri, Sep 27, 2002 at 12:44:18PM -0700, Andrew Morton wrote:
> If the fs was mounted -o sync or -o dirsync, those creates would involve
> synchronous I/O inside i_sem.  So the problem is potentially more serious
> in such a setup.
> Even then, do we care?  Well hrm.  One page of ZONE_NORMAL per process
> doesn't sound like the end of the world...

Well, it's one of the larger contributors to one of my OOM scenarios,
which is why I asked willy to do it. Also consider /tmp/ ...


Cheers,
Bill

  reply	other threads:[~2002-09-27 20:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-27 14:02 simultaneous creates in a directory Matthew Wilcox
2002-09-27 19:44 ` Andrew Morton
2002-09-27 20:44   ` William Lee Irwin III [this message]
2002-09-27 21:08     ` Andrew Morton

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=20020927204425.GT22942@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=akpm@digeo.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=willy@debian.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.