From: Andrew Morton <akpm@osdl.org>
To: IWAMOTO Toshihiro <iwamoto@valinux.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: O_DIRECT leaks memory on linux-2.6.0-test9
Date: Thu, 20 Nov 2003 23:55:30 -0800 [thread overview]
Message-ID: <20031120235530.3d09882f.akpm@osdl.org> (raw)
In-Reply-To: <20031121073411.665A27007C@sv1.valinux.co.jp>
IWAMOTO Toshihiro <iwamoto@valinux.co.jp> wrote:
>
> It'll take a while to leak a noticable amount of memory. So I reduced
> the amount of memory using a boot option.
Well I'll be darned. I took a new version of fsstress and it happens here
too. We're leaking anonymous memory. -mm doesn't do any better, either.
next prev parent reply other threads:[~2003-11-21 7:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-21 6:18 IWAMOTO Toshihiro
2003-11-21 7:17 ` Andrew Morton
2003-11-21 7:34 ` IWAMOTO Toshihiro
2003-11-21 7:55 ` Andrew Morton [this message]
2003-11-21 8:24 ` Gene Heskett
2003-11-21 8:40 ` Andrew Morton
2003-11-21 14:02 ` Gene Heskett
2003-11-21 14:25 ` Gene Heskett
2003-11-21 14:48 ` Gene Heskett
2003-12-13 15:13 ` Oops on module insertion of 3c509/3c95x Alexander Nyberg
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=20031120235530.3d09882f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=iwamoto@valinux.co.jp \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®