From: "Mitani" <mitani@ryobi.co.jp>
To: 'Randy Dunlap' <rdunlap@xenotime.net>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] fix "hugetlb" several tests
Date: Fri, 16 Apr 2010 11:42:39 +0900 [thread overview]
Message-ID: <000001cadd0e$7b35e250$71a1a6f0$@co.jp> (raw)
In-Reply-To: <20100414081953.7356b407.rdunlap@xenotime.net>
> -----Original Message-----
> From: Randy Dunlap [mailto:rdunlap@xenotime.net]
> Sent: Thursday, April 15, 2010 12:20 AM
> To: Mitani
> Cc: 'Garrett Cooper'; ltp-list@lists.sourceforge.net
> Subject: Re: [LTP] [PATCH] fix "hugetlb" several tests
>
> On Wed, 14 Apr 2010 17:58:17 +0900 Mitani wrote:
>
> > Hi,
> >
> > I suggest new patch.
> >
> > Signed-off-by: Tomonori Mitani <mitani@ryobi.co.jp>
>
> This one is OK with me also, but...
>
> Is it possible to determine the difference between a kernel that does
> not support hugepages at all and a kernel that does support hugepages
> but just does not have enough of them allocated?
>
> or maybe we don't care about this difference. Do we?
>
I cannot give a good opinion because I'm not a creator of these test
programs, but ...
I think that the difference of test refusal reason isn't so important.
How about following message? :
------------
Not support Hugepages or not enough available Hugepages
------------
If users read above message, they will examine a reason by themselves
and will do appropriate measures (set an enough hugepages value or
gave up this test), I think.
Regards--
-Tomonori Mitani
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2010-04-16 2:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 6:58 [LTP] [PATCH] fix "hugetlb" several tests Mitani
2010-04-13 15:03 ` Randy Dunlap
2010-04-14 2:17 ` Mitani
2010-04-14 6:17 ` Garrett Cooper
2010-04-14 8:58 ` Mitani
2010-04-14 9:18 ` Ryan Wang
2010-04-14 9:30 ` Garrett Cooper
2010-04-15 0:56 ` Mitani
2010-04-15 6:54 ` Rishikesh K Rajak
2010-04-15 8:42 ` Garrett Cooper
2010-04-16 1:33 ` Mitani
2010-04-16 5:15 ` Garrett Cooper
2010-04-14 15:19 ` Randy Dunlap
2010-04-16 2:42 ` Mitani [this message]
2010-04-16 5:05 ` Garrett Cooper
2010-04-16 9:23 ` Mitani
2010-04-16 15:12 ` Randy Dunlap
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='000001cadd0e$7b35e250$71a1a6f0$@co.jp' \
--to=mitani@ryobi.co.jp \
--cc=ltp-list@lists.sourceforge.net \
--cc=rdunlap@xenotime.net \
/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