From: Toshiyuki Okajima <toshi.okajima@jp.fujitsu.com>
To: linux-ext4@vger.kernel.org
Cc: Jan Kara <jack@suse.cz>
Subject: Re: (take 2)[PATCH] JBD: positively dispose the unmapped data buffers in journal_commit_transaction
Date: Mon, 30 Jun 2008 10:53:46 +0900 [thread overview]
Message-ID: <48683CAA.5040401@jp.fujitsu.com> (raw)
In-Reply-To: <20080626171857.GA20004@atrey.karlin.mff.cuni.cz>
Hi,
Jan Kara wrote:
>> Hi,
>>
>> Jan Kara wrote:
>>> Hi,
>>>
>>>> I updated my patch and introduction article for it by reflecting
>>>> the comment of Andrew's.
>> <SNIP>
>>>> Signed-off-by: Toshiyuki Okajima <toshi.okajima@jp.fujitsu.com>
>>> I agree with the change. It's true that we can leave some anonymous
>>> pages behind and it's nicer to the MM to release them earlier when we
>>> know they will be never needed again. The patch looks fine to me, you
>>> can add
>>> Acked-by: Jan Kara <jack@suse.cz>
>> Thank you for confirming.
> Please keep me CCed (use group reply), thanks. I sometimes don't have
> time for reading mailing lists or just skim through them so I can easily
> miss replies...
OK, I will keep you CCed next time.
>>> How much have you stressed the patched kernel? I suggest you use
>>> fsxlinux and put some memory pressure to the system...
>> I have stressed it for 72 or more hours.
>> Stresser does:
>> - allocates/frees big memory(1.7GB) which was almost system
>> memory size(2GB) repeatedly.
> OK, I suppose you also wrote something to the memory (otherwise it
> won't be really allocated).
I forgot to explain. You are right.
It writes something to each of all pages.
>> Confirmation of integrity of patched Filesystem(jbd) does:
>> - creates files, and copies 3 files from created each file
>> (3 copies run concurrently), and confirms whether there is
>> no difference between created files and copied files.
>> (20 processes runs these works concurrently and repeatedly.)
>> Above 2 jobs run concurrently.
> This sounds reasonable. fsxlinux does actually something similar but
> it also stresses mmaped accesses and truncate patch. In this case, what
> you did should be enough.
>
> Honza
I wrote only abstract of my long run test at previous mail,
but my test does also mmaped accesses.
So, it seems my test works really the same as fsxlinux...
Thanks,
---
Toshiyuki Okajima
prev parent reply other threads:[~2008-06-30 1:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 11:00 [PATCH] JBD: positively dispose the unmapped data buffers in journal_commit_transaction Toshiyuki Okajima
2008-06-24 2:27 ` Andrew Morton
2008-06-24 8:01 ` Toshiyuki Okajima
2008-06-25 7:33 ` (take 2)[PATCH] " Toshiyuki Okajima
2008-06-25 20:39 ` Jan Kara
2008-06-26 6:16 ` Toshiyuki Okajima
2008-06-26 17:18 ` Jan Kara
2008-06-30 1:53 ` Toshiyuki Okajima [this message]
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=48683CAA.5040401@jp.fujitsu.com \
--to=toshi.okajima@jp.fujitsu.com \
--cc=jack@suse.cz \
--cc=linux-ext4@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 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.