From: Chris Mason <mason@suse.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Daniel Phillips <phillips@bonn-fries.net>,
Ben LaHaise <bcrl@redhat.com>,
Rik van Riel <riel@conectiva.com.br>,
linux-mm@kvack.org
Subject: Re: [RFC][DATA] re "ongoing vm suckage"
Date: Tue, 07 Aug 2001 16:22:51 -0400 [thread overview]
Message-ID: <493160000.997215771@tiny> (raw)
In-Reply-To: <Pine.LNX.4.33.0108071251100.3977-100000@penguin.transmeta.com>
On Tuesday, August 07, 2001 12:52:11 PM -0700 Linus Torvalds
<torvalds@transmeta.com> wrote:
> On Tue, 7 Aug 2001, Chris Mason wrote:
>>
>> Linus seemed pretty sure kswapd wasn't deadlocked, but though I would
>> mention this anyway....
>
> The thing that Leonard seems able to repeat pretty well is just doing a
> "mke2fs" on a big partition. I don't think xfs is involved there at all.
It depends, mke2fs could be just another GFP_NOFS process waiting around
for kswapd to free buffers. If a journaled filesystem is there, and it is
locking up kswapd, any heavy buffer allocator could make the problem seem
worse.
But, if you mean XFS is not mounted at all, I'm way off ;-)
-chris
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2001-08-07 20:22 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-03 23:44 Ben LaHaise
2001-08-04 1:29 ` Rik van Riel
2001-08-04 3:06 ` Daniel Phillips
2001-08-04 3:13 ` Linus Torvalds
2001-08-04 3:23 ` Rik van Riel
2001-08-04 3:35 ` Linus Torvalds
2001-08-04 3:26 ` Ben LaHaise
2001-08-04 3:34 ` Rik van Riel
2001-08-04 3:38 ` Linus Torvalds
2001-08-04 3:48 ` Linus Torvalds
2001-08-04 4:14 ` Ben LaHaise
2001-08-04 4:20 ` Linus Torvalds
2001-08-04 4:39 ` Ben LaHaise
2001-08-04 4:47 ` Linus Torvalds
2001-08-04 5:13 ` Ben LaHaise
2001-08-04 5:28 ` Linus Torvalds
2001-08-04 6:37 ` Linus Torvalds
2001-08-04 5:38 ` Marcelo Tosatti
2001-08-04 7:13 ` Rik van Riel
2001-08-04 23:28 ` [PATCH] Unlazy activate (was: re "ongoing vm suckage") Daniel Phillips
2001-08-04 14:22 ` [RFC][DATA] re "ongoing vm suckage" Mike Black
2001-08-04 17:08 ` Linus Torvalds
2001-08-04 20:54 ` Jonathan Morton
2001-08-05 4:19 ` Michael Rothwell
2001-08-05 18:40 ` Marcelo Tosatti
2001-08-05 20:20 ` Linus Torvalds
2001-08-06 20:32 ` Rob Landley
2001-08-05 15:24 ` Mike Black
2001-08-05 20:04 ` Linus Torvalds
2001-08-05 20:23 ` Alan Cox
2001-08-05 20:33 ` Linus Torvalds
2001-08-04 16:21 ` Mark Hemment
2001-08-07 15:45 ` Ben LaHaise
2001-08-07 16:22 ` Linus Torvalds
2001-08-07 16:51 ` Ben LaHaise
2001-08-07 17:08 ` Linus Torvalds
2001-08-07 18:17 ` Andrew Morton
2001-08-07 18:40 ` Ben LaHaise
2001-08-07 21:33 ` Daniel Phillips
2001-08-07 21:33 ` Linus Torvalds
2001-08-07 17:04 ` Linus Torvalds
2001-08-07 17:11 ` Rik van Riel
2001-08-07 19:12 ` Linus Torvalds
2001-08-07 19:21 ` Rik van Riel
2001-08-07 20:50 ` Linus Torvalds
2001-08-07 23:36 ` Linus Torvalds
2001-08-07 17:26 ` Chris Mason
2001-08-07 18:13 ` Daniel Phillips
2001-08-07 18:40 ` Chris Mason
2001-08-07 19:52 ` Linus Torvalds
2001-08-07 20:22 ` Chris Mason [this message]
2001-08-08 1:08 ` Theodore Tso
2001-08-08 1:13 ` Linus Torvalds
2001-08-08 2:25 ` Marcelo Tosatti
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=493160000.997215771@tiny \
--to=mason@suse.com \
--cc=bcrl@redhat.com \
--cc=linux-mm@kvack.org \
--cc=phillips@bonn-fries.net \
--cc=riel@conectiva.com.br \
--cc=torvalds@transmeta.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