From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Theodore Tso <tytso@mit.edu>,
Valdis.Kletnieks@vt.edu, David Chinner <dgc@sgi.com>,
Valerie Henson <val@vahconsulting.com>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org,
Andreas Dilger <adilger@clusterfs.com>, Ric Wheeler <ric@emc.com>,
marcelo@kvack.org
Subject: Re: [RFC] Parallelize IO for e2fsck
Date: Tue, 22 Jan 2008 12:57:53 -0200 [thread overview]
Message-ID: <20080122145753.GC32529@ghostprotocols.net> (raw)
In-Reply-To: <20080122144052.GC17804@mit.edu>
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
next prev parent reply other threads:[~2008-01-22 14:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <70b6f0bf0801161322k2740a8dch6a0d6e6e112cd2d0@mail.gmail.com>
2008-01-16 21:30 ` [RFC] Parallelize IO for e2fsck Valerie Henson
2008-01-18 1:15 ` David Chinner
2008-01-18 1:43 ` Valerie Henson
2008-01-21 23:00 ` Andreas Dilger
2008-01-22 3:38 ` David Chinner
2008-01-22 4:17 ` Valdis.Kletnieks
2008-01-22 7:00 ` Andreas Dilger
2008-01-22 13:05 ` Alan Cox
2008-01-22 14:40 ` Theodore Tso
2008-01-22 14:57 ` Arnaldo Carvalho de Melo [this message]
2008-01-28 19:30 ` Pavel Machek
2008-01-28 19:56 ` Theodore Tso
2008-01-28 20:01 ` Pavel Machek
2008-02-03 13:51 ` KOSAKI Motohiro
2008-01-29 8:29 ` david
2008-01-22 7:05 ` Andreas Dilger
2008-01-22 8:16 ` David Chinner
2008-01-22 17:42 ` Bryan Henderson
[not found] <9Mo9w-7Ws-25@gated-at.bofh.it>
[not found] ` <9Mo9w-7Ws-23@gated-at.bofh.it>
[not found] ` <9OdWm-7uN-25@gated-at.bofh.it>
[not found] ` <9Oi9A-5EJ-3@gated-at.bofh.it>
[not found] ` <9OiMg-6IC-1@gated-at.bofh.it>
[not found] ` <9OlqL-2xG-3@gated-at.bofh.it>
[not found] ` <9Orda-3ub-45@gated-at.bofh.it>
2008-01-24 17:32 ` Bodo Eggert
2008-01-24 22:07 ` Andreas Dilger
2008-01-24 23:08 ` Adrian Bunk
2008-01-24 23:40 ` Theodore Tso
2008-01-25 0:25 ` Zan Lynx
2008-01-25 11:09 ` Andreas Dilger
2008-01-26 0:55 ` Zan Lynx
2008-01-26 11:56 ` KOSAKI Motohiro
2008-01-26 12:32 ` KOSAKI Motohiro
[not found] <alpine.LSU.0.999.0801252338460.26260@be1.lrz>
2008-01-26 1:55 ` Bryan Henderson
2008-01-26 13:21 ` Theodore Tso
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=20080122145753.GC32529@ghostprotocols.net \
--to=acme@redhat.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=adilger@clusterfs.com \
--cc=dgc@sgi.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@kvack.org \
--cc=ric@emc.com \
--cc=tytso@mit.edu \
--cc=val@vahconsulting.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).