From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: mqueue perf data
Date: Tue, 10 Dec 2013 15:49:38 +0800 [thread overview]
Message-ID: <52A6C792.3010500@cn.fujitsu.com> (raw)
Hi Fengguang,
Do we need to stat out the perf data of mqueue test in kernel_selftests?
It's like following.
Thanks,
Wanlong Gao
# make run_tests -C mqueue
make: Entering directory `/git/linux/tools/testing/selftests/mqueue'
Initial system state:
Using queue path: /test1
RLIMIT_MSGQUEUE(soft): 819200
RLIMIT_MSGQUEUE(hard): 819200
Maximum Message Size: 8192
Maximum Queue Size: 10
Default Message Size: 8192
Default Queue Size: 10
Adjusted system state for testing:
RLIMIT_MSGQUEUE(soft): 819200
RLIMIT_MSGQUEUE(hard): 819200
Maximum Message Size: 8192
Maximum Queue Size: 10
Default Message Size: 8192
Default Queue Size: 10
Test series 1, behavior when no attr struct passed to mq_open:
Kernel supports setting defaults separately from maximums: PASS
Given sane values, mq_open without an attr struct succeeds: PASS
Kernel properly honors default setting knobs: PASS
Kernel properly limits default values to lesser of default/max: PASS
Kernel properly fails to create queue when defaults would
exceed rlimit: PASS
Test series 2, behavior when attr struct is passed to mq_open:
Queue open in excess of rlimit max when euid = 0 failed: PASS
Queue open with mq_maxmsg > limit when euid = 0 succeeded: PASS
Queue open with mq_msgsize > limit when euid = 0 succeeded: PASS
Queue open with total size > 2GB when euid = 0 failed: PASS
Queue open in excess of rlimit max when euid = 99 failed: PASS
Queue open with mq_maxmsg > limit when euid = 99 failed: PASS
Queue open with mq_msgsize > limit when euid = 99 failed: PASS
Queue open with total size > 2GB when euid = 99 failed: PASS
Initial system state:
Using queue path: /mq_perf_tests
RLIMIT_MSGQUEUE(soft): 819200
RLIMIT_MSGQUEUE(hard): 819200
Maximum Message Size: 8192
Maximum Queue Size: 10
Nice value: 0
Adjusted system state for testing:
RLIMIT_MSGQUEUE(soft): (unlimited)
RLIMIT_MSGQUEUE(hard): (unlimited)
Maximum Message Size: 16777216
Maximum Queue Size: 65530
Nice value: -20
Continuous mode: (disabled)
CPUs to pin: 3
Queue /mq_perf_tests created:
mq_flags: O_NONBLOCK
mq_maxmsg: 65530
mq_msgsize: 16
mq_curmsgs: 0
Started mqueue performance test thread on CPU 3
Max priorities: 32768
Clock resolution: 1 nsec
Test #1: Time send/recv message, queue empty
(10000000 iterations)
Send msg: 4.50690280s total time
405 nsec/msg
Recv msg: 4.123621560s total time
412 nsec/msg
Test #2a: Time send/recv message, queue full, constant prio
(100000 iterations)
Filling queue...done. 0.14554407s
Testing...done.
Send msg: 0.40292962s total time
402 nsec/msg
Recv msg: 0.40605786s total time
406 nsec/msg
Draining queue...done. 0.15010003s
Test #2b: Time send/recv message, queue full, increasing prio
(100000 iterations)
Filling queue...done. 0.25628197s
Testing...done.
Send msg: 0.53792862s total time
537 nsec/msg
Recv msg: 0.52323416s total time
523 nsec/msg
Draining queue...done. 0.17617835s
Test #2c: Time send/recv message, queue full, decreasing prio
(100000 iterations)
Filling queue...done. 0.26939894s
Testing...done.
Send msg: 0.55733128s total time
557 nsec/msg
Recv msg: 0.51363749s total time
513 nsec/msg
Draining queue...done. 0.19254167s
Test #2d: Time send/recv message, queue full, random prio
(100000 iterations)
Filling queue...done. 0.28530211s
Testing...done.
Send msg: 0.59583951s total time
595 nsec/msg
Recv msg: 0.55122718s total time
551 nsec/msg
Draining queue...done. 0.19537439s
make: Leaving directory `/git/linux/tools/testing/selftests/mqueue'
next reply other threads:[~2013-12-10 7:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 7:49 Wanlong Gao [this message]
2013-12-10 8:13 ` mqueue perf data Fengguang Wu
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=52A6C792.3010500@cn.fujitsu.com \
--to=gaowanlong@cn.fujitsu.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@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.