From: Miao Xie <miaox@cn.fujitsu.com>
To: Subrata Modak <subrata@linux.vnet.ibm.com>
Cc: LTP Mailing List <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH] Add new testcases for ext4 new features
Date: Mon, 26 Oct 2009 16:07:33 +0900 [thread overview]
Message-ID: <4AE54AB5.7070501@cn.fujitsu.com> (raw)
In-Reply-To: <20091024084906.11570.79144.sendpatchset@subratamodak.linux.ibm.com>
Hi, Mr. Modak
on 2009-10-24 17:49, Subrata Modak wrote:
> The SEGMENTATION Fault in ffsb was there, but i found the problem and the
> following patch should be applied to fix that problem:
Thanks.
>
> Issues/Observations:
>
> 1) The test was running for more than 44 hours, so, i had to terminate it.
> I had no idea of how long the test will run. Can you please update:
> ltp-full-20090930/testcases/kernel/fs/ext4-new-features/README file
> for the duration of the test run under nornal circumstance(s) ?
> Does it depend upon the size of the partition (i ran it on a 680 GB
> LVM this time) ??
> And i also gave LTP a nice value of -20 this time to speed up the
> process, still it was taking huge time.
The partition that you selected is too large, so the test program spend
much time to write the data into partition. It is unnecessary. I think
a 5-10G partition is enough.
> 2) Good news is that, the CODE COVERAGE generated on 2.6.30 kernel
> was more than 50% for lines, and 61% for EXT functions. Thatś a good news.
> Can you please device strategies for increasing the code coverage
> by writing tests in those areas which remained untouched.
We used the other filesystem testcases in the LTP to make up for the shortage
of this testcases. This testcases is just used to test ext4 new features.
> 3) Due to changes in the Makefile structures in LTP made by Garret
> in the first week of Oct 2009, your patch will not apply as-is. Can you
> please rebase your patch over the latest Makefile infrastructre, include
> the above comments and resend it once again.
Ok, I'll do it.
Regards.
Miao
>
> Thanks once again for writing these tests and taking the trouble
> to fix the integration issues with LTP. Following are the system
> parameters where i executed these tests:
>
> # uname -a
> Linux 2.6.31 #1 SMP Tue Oct 20 22:57:16 IST 2009 i686 i686 i386 GNU/Linux
>
> # cat /etc/issue
> Welcome to SUSE Linux Enterprise Server 11 (i586) - Kernel \r (\l).
>
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-10-26 7:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-24 8:49 [LTP] [PATCH] Add new testcases for ext4 new features Subrata Modak
2009-10-24 8:50 ` Subrata Modak
2009-10-26 7:07 ` Miao Xie [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-28 14:17 Subrata Modak
2009-10-06 7:31 ` Miao Xie
2009-09-24 1:25 Miao Xie
2009-09-24 6:23 ` Subrata Modak
2009-10-09 13:43 ` Cyril Hrubis
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=4AE54AB5.7070501@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=subrata@linux.vnet.ibm.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