All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: William Lee Irwin III <wli@holomorphy.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 14:08:38 -0700	[thread overview]
Message-ID: <3D94C8D6.5C07D7F2@digeo.com> (raw)
In-Reply-To: 20020927204425.GT22942@holomorphy.com

William Lee Irwin III wrote:
> 
> > 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,

doom scenarios more like ;)

> which is why I asked willy to do it. Also consider /tmp/ ...
> 

Does Matthew's patch actually work?  Seems that we have to
perform lookups while holding that memory, and that requires
taking i_sem.

It's hard to get very excited about the seriousness of this
problem, I must say.

Any idea why the opens are taking so long?  Maybe someone is
throttled on writeback while holding i_sem?

It would be interesting to actually hunt down the current i_sem
holder and see what he's up to.  That's pretty easy:

struct task_struct *wli_task;

	down(&dir->i_sem);
	wli_task = current;

then go poke at wli_task in kgdb.

      reply	other threads:[~2002-09-27 21:08 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
2002-09-27 21:08     ` Andrew Morton [this message]

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