From: Ted Ts'o <tytso@mit.edu>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Rik van Riel <riel@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Chris Mason <chris.mason@oracle.com>,
Dave Chinner <david@fromorbit.com>, Jan Kara <jack@suse.cz>,
Jens Axboe <axboe@kernel.dk>, Mel Gorman <mel@csn.ul.ie>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Christoph Hellwig <hch@lst.de>, linux-mm <linux-mm@kvack.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: ext4 memory leak?
Date: Tue, 7 Dec 2010 11:38:20 -0500 [thread overview]
Message-ID: <20101207163820.GF24607@thunk.org> (raw)
In-Reply-To: <20101207152120.GA28220@localhost>
On Tue, Dec 07, 2010 at 11:21:20PM +0800, Wu Fengguang wrote:
> On Tue, Dec 07, 2010 at 10:33:51PM +0800, Wu Fengguang wrote:
> > > In a simple dd test on a 8p system with "mem=256M", I find the light
> >
> > When increasing to 10 concurrent dd tasks, I managed to crash ext4..
> > (2 concurrent dd's are OK, with very good write performance.)
What was the dd command line? Specifically, how big were the file
writes? I haven't been able to replicate a leak. I'll try on a small
system seeing if I can replicate an OOM kill, but I'm not seeing a
leak. (i.e., after the dd if=/dev/zero of=/test/$i" jobs) are
finished, the memory utilization looks normal and I don't see any
obvious slab leaks.
- Ted
WARNING: multiple messages have this Message-ID (diff)
From: Ted Ts'o <tytso@mit.edu>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Rik van Riel <riel@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Chris Mason <chris.mason@oracle.com>,
Dave Chinner <david@fromorbit.com>, Jan Kara <jack@suse.cz>,
Jens Axboe <axboe@kernel.dk>, Mel Gorman <mel@csn.ul.ie>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Christoph Hellwig <hch@lst.de>, linux-mm <linux-mm@kvack.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: ext4 memory leak?
Date: Tue, 7 Dec 2010 11:38:20 -0500 [thread overview]
Message-ID: <20101207163820.GF24607@thunk.org> (raw)
In-Reply-To: <20101207152120.GA28220@localhost>
On Tue, Dec 07, 2010 at 11:21:20PM +0800, Wu Fengguang wrote:
> On Tue, Dec 07, 2010 at 10:33:51PM +0800, Wu Fengguang wrote:
> > > In a simple dd test on a 8p system with "mem=256M", I find the light
> >
> > When increasing to 10 concurrent dd tasks, I managed to crash ext4..
> > (2 concurrent dd's are OK, with very good write performance.)
What was the dd command line? Specifically, how big were the file
writes? I haven't been able to replicate a leak. I'll try on a small
system seeing if I can replicate an OOM kill, but I'm not seeing a
leak. (i.e., after the dd if=/dev/zero of=/test/$i" jobs) are
finished, the memory utilization looks normal and I don't see any
obvious slab leaks.
- Ted
--
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/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-12-07 16:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 6:44 [PATCH] writeback: enabling-gate for light dirtied bdi Wu Fengguang
2010-12-05 6:44 ` Wu Fengguang
2010-12-05 14:04 ` Rik van Riel
2010-12-05 14:04 ` Rik van Riel
2010-12-07 13:11 ` [PATCH] writeback: safety margin for bdi stat errors Wu Fengguang
2010-12-07 13:11 ` Wu Fengguang
[not found] ` <20101207143351.GA23377@localhost>
2010-12-07 15:21 ` ext4 memory leak? Wu Fengguang
2010-12-07 16:38 ` Ted Ts'o [this message]
2010-12-07 16:38 ` Ted Ts'o
2010-12-08 2:40 ` Wu Fengguang
2010-12-08 2:40 ` Wu Fengguang
2010-12-08 3:07 ` Theodore Tso
2010-12-08 3:07 ` Theodore Tso
2010-12-08 6:10 ` Wu Fengguang
2010-12-08 6:10 ` Wu Fengguang
2010-12-07 17:34 ` [PATCH] writeback: safety margin for bdi stat errors Rik van Riel
2010-12-07 17:34 ` Rik van Riel
2010-12-08 0:51 ` [PATCH] writeback: enabling-gate for light dirtied bdi Andrew Morton
2010-12-08 0:51 ` Andrew Morton
2010-12-08 4:04 ` Wu Fengguang
2010-12-08 4:04 ` Wu Fengguang
2010-12-08 4:30 ` [PATCH v2] " Wu Fengguang
2010-12-08 4:30 ` Wu Fengguang
2010-12-08 4:37 ` [PATCH v2] writeback: safety margin for bdi stat error Wu Fengguang
2010-12-08 4:37 ` Wu Fengguang
2010-12-08 15:31 ` [PATCH v2] writeback: enabling-gate for light dirtied bdi Wu Fengguang
2010-12-08 15:31 ` Wu Fengguang
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=20101207163820.GF24607@thunk.org \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=chris.mason@oracle.com \
--cc=david@fromorbit.com \
--cc=fengguang.wu@intel.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=peterz@infradead.org \
--cc=riel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.