From: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>
To: "Diwakar Sharma (RBEI/ECF3)" <Diwakar.Sharma@in.bosch.com>,
"ltp-list@lists.sourceforge.net" <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] - Kernel - tunable max_map_count test failure - 20140115-46-g2368cd4
Date: Mon, 05 May 2014 17:01:49 +0400 [thread overview]
Message-ID: <53678BBD.80607@oracle.com> (raw)
In-Reply-To: <46CD92664333704E8A06E512A60A9E9F2AD2C0B12F@SGPMBX02.APAC.bosch.com>
On 05/05/2014 10:52 AM, Diwakar Sharma (RBEI/ECF3) wrote:
> Hi,
Hi!
>
> I was getting the max_map_count test failed. It looked to me failing at filter_map function. The platform I'm working on is an i686 architecture running on Virtualbox.
> I added below additional macro condition and it's passing now. I want to understand if not including i686/386 was intentional originally for some reason? Also vdso part I added additionaly.
>
> #elif defined(__i686__) || defined(__i386__)
> static int filter_map(char *line)
> {
> char buf[BUFSIZ];
> int ret;
>
> ret = sscanf(line, "%*p-%*p %*4s %*p %*2d:%*2d %*d %s", buf);
> if (ret != 1)
> return 0;
>
> return ((strcmp(buf, "[vdso]") == 0) | (strcmp(buf, "[vsyscall]") == 0));
> }
>
>
> On another similar architecture (but the actual h/w board), the same code gives messages like "4096 map entries in total, but expected 4096 entries" and reported FAIL, implying map_count and max_maps is same ( Contrary to map_count==max_maps+1 ). How do we analyze this scenario? Does this mean it is not exceeding by one for sysctl setting? How to verify that.
>
Which kernel version do you use? I want to check this test case in my
environment.
Thanks.
PS: Also look at this thread
http://sourceforge.net/p/ltp/mailman/ltp-list/thread/52009D26.4030609%40oracle.com/
>
> Thanks and Regards
> Diwakar Sharma
>
>
>
> ------------------------------------------------------------------------------
> Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
> • 3 signs your SCM is hindering your productivity
> • Requirements for releasing software faster
> • Expert tips and advice for migrating your SCM now
> http://p.sf.net/sfu/perforce
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
>
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-05-05 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 6:52 [LTP] - Kernel - tunable max_map_count test failure - 20140115-46-g2368cd4 Diwakar Sharma (RBEI/ECF3)
2014-05-05 13:01 ` Stanislav Kholmanskikh [this message]
2014-05-05 13:06 ` Diwakar Sharma (RBEI/ECF3)
2014-05-06 8:57 ` Stanislav Kholmanskikh
2014-05-07 8:47 ` Diwakar Sharma (RBEI/ECF3)
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=53678BBD.80607@oracle.com \
--to=stanislav.kholmanskikh@oracle.com \
--cc=Diwakar.Sharma@in.bosch.com \
--cc=ltp-list@lists.sourceforge.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