[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080122145753.GC32529@ghostprotocols.net>
Date: Tue, 22 Jan 2008 12:57:53 -0200
From: Arnaldo Carvalho de Melo <acme@...hat.com>
To: Theodore Tso <tytso@....edu>, Valdis.Kletnieks@...edu,
David Chinner <dgc@....com>,
Valerie Henson <val@...consulting.com>,
linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org,
linux-kernel@...r.kernel.org,
Andreas Dilger <adilger@...sterfs.com>,
Ric Wheeler <ric@....com>, marcelo@...ck.org
Subject: Re: [RFC] Parallelize IO for e2fsck
Em Tue, Jan 22, 2008 at 09:40:52AM -0500, Theodore Tso escreveu:
> On Tue, Jan 22, 2008 at 12:00:50AM -0700, Andreas Dilger wrote:
> > > AIX had SIGDANGER some 15 years ago. Admittedly, that was sent when
> > > the system was about to hit OOM, not when it was about to start swapping.
> >
> > I'd tried to advocate SIGDANGER some years ago as well, but none of
> > the kernel maintainers were interested. It definitely makes sense
> > to have some sort of mechanism like this. At the time I first brought
> > it up it was in conjunction with Netscape using too much cache on some
> > system, but it would be just as useful for all kinds of other memory-
> > hungry applications.
>
> It's been discussed before, but I suspect the main reason why it was
> never done is no one submitted a patch. Also, the problem is actually
> a pretty complex one. There are a couple of different stages where
> you might want to send an alert to processes:
Isn't Marcelo, Riel and some other people working on memory
notifications?
- Arnaldo
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists