From: chrubis@suse.cz
To: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>
Cc: vasily.isaenko@oracle.com, ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH V2 2/2] msgctl11: process message queues by portions
Date: Tue, 25 Feb 2014 15:00:17 +0100 [thread overview]
Message-ID: <20140225140017.GC14376@rei> (raw)
In-Reply-To: <530CA0A3.403@oracle.com>
Hi!
> > On my systems /proc/sys/kernel/pid_max is set to 32768 and MSGMNI is
> > from 2000 to 7000 on most of the machines I've seen. So the value of
> > maxnkids was between 1 and 4 previously but it defaults to 10 after this
> > patch which increases the test runtime by minute or two.
> >
> > Thinking of this again the most behavior preserving change would be:
> >
> > if ((MSGMNI * MAXNKIDS * 2) > (free_pids / 2))
> > maxnkids = MAX(1, ((free_pids / 4) / MSGMNI));
> >
> > Which would scale the number of kids to the free pids but will not abort
> > the test if there is not enough free pids. The drawback is that the code
> > is complicated enough even without this change...
> >
>
> According to the definition of recompute_msgmni() function (ipc/msg.c)
> the limit by which the kernel may increase msgmni automatically is
> IPCMNI. And IPCMNI is defined to be 32768 (include/linux/ipc.h).
>
> So yes, the above approach (using MAX) should work on most systems
> (maybe even all. I'm not sure about embedded stuff) where neither
> pid_max nor msgmni values were modified manually. Manually changing
> pid_max and/or msgmni values we can break the test.
>
> Actually, I don't like the MAX-variant, because of the drawback you
> mentioned. But the MAX-variant is sufficient for my needs.
>
> So which patch set to prepare? :)
I would be inclined to set the default maxnkids value to something more
reasonable than 10, perhaps 2 or 3 would be a good compromise between
the test runtime and the amount of system stress the test does.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-02-25 14:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 13:39 [LTP] [PATCH] msgctl11: process message queues by portions Stanislav Kholmanskikh
2014-02-06 13:29 ` chrubis
[not found] ` <52F9EE70.9040700@oracle.com>
2014-02-11 14:23 ` chrubis
2014-02-11 15:19 ` [LTP] [PATCH V2 1/2] msgctl11: cleanup and fflush removed Stanislav Kholmanskikh
2014-02-11 15:19 ` [LTP] [PATCH V2 2/2] msgctl11: process message queues by portions Stanislav Kholmanskikh
2014-02-21 18:11 ` chrubis
[not found] ` <530C5E99.6050809@oracle.com>
2014-02-25 12:25 ` chrubis
[not found] ` <530CA0A3.403@oracle.com>
2014-02-25 14:00 ` chrubis [this message]
2014-02-25 14:40 ` [LTP] [PATCH V3 1/2] msgctl11: cleanup and fflush removed Stanislav Kholmanskikh
2014-02-25 14:40 ` [LTP] [PATCH V3 2/2] msgctl11: process message queues by portions Stanislav Kholmanskikh
2014-03-05 10:45 ` chrubis
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=20140225140017.GC14376@rei \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=stanislav.kholmanskikh@oracle.com \
--cc=vasily.isaenko@oracle.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