From: "Stephen C. Tweedie" <sct@redhat.com>
To: Rik van Riel <H.H.vanRiel@phys.uu.nl>
Cc: Jeffrey Hundstad <jeffrey.hundstad@mankato.msus.edu>,
Linux MM <linux-mm@kvack.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: useless report -- perhaps memory allocation problems in 2.1.12[678]
Date: Tue, 17 Nov 1998 11:21:22 GMT [thread overview]
Message-ID: <199811171121.LAA00897@dax.scot.redhat.com> (raw)
In-Reply-To: <Pine.LNX.3.96.981116152322.20349E-100000@mirkwood.dummy.home>
Hi,
In article
<Pine.LNX.3.96.981116152322.20349E-100000@mirkwood.dummy.home>, Rik van
Riel <H.H.vanRiel@phys.uu.nl> writes:
> In 2.1.127+ the freeing of memory is done in the context of
> programs themselves too
It always has done: it's just a bit better at it in some situations now.
> and the whole system is busy freeing memory. This means that the
> kswapd-loop has now been migrated into other contexts as well. This,
> together with the fact that kswapd never blocks on disk access any
> more,
Yes it does. We don't pass GFP_WAIT to swap_out(), but that just means
that the swapout will be done asynchronously. We are still free to
write stuff out to swap, and in fact once we hit the limit on
outstanding IOs we may well block in the write.
--Stephen
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next prev parent reply other threads:[~1998-11-17 11:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199811131746.LAA23512@mail.mankato.msus.edu>
1998-11-16 14:27 ` Rik van Riel
1998-11-17 11:21 ` Stephen C. Tweedie [this message]
1998-11-17 20:18 ` Rik van Riel
1998-11-17 23:14 ` Linus Torvalds
1998-11-18 1:09 ` Stephen C. Tweedie
1998-11-18 1:21 ` Linus Torvalds
1998-11-18 1:41 ` Linus Torvalds
1998-11-18 8:58 ` Rik van Riel
1998-11-18 9:19 ` Stephen C. Tweedie
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=199811171121.LAA00897@dax.scot.redhat.com \
--to=sct@redhat.com \
--cc=H.H.vanRiel@phys.uu.nl \
--cc=jeffrey.hundstad@mankato.msus.edu \
--cc=linux-mm@kvack.org \
--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