From: John McNamara <john.mcnamara@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] mk: added make target to print out system info
Date: Tue, 24 Mar 2015 14:52:58 +0000 [thread overview]
Message-ID: <1427208779-16548-1-git-send-email-john.mcnamara@intel.com> (raw)
Added a 'make system_info' target to print out system info related to
DPDK. This is intended as output that can be attached to bug reports.
This is related to the recent call for tools brainstorming by Thomas.
http://dpdk.org/ml/archives/dev/2015-March/015499.html
Bug reports to the DPDK mailing list rarely have enough information and
require several follow-up questions to determine the version of software, the
OS, the compiler etc.
This 'make' target prints out some useful system information that can be
attached to an email. There is no guarantee that the end user will do this but
at least it can be documented and we can point them to it.
Suggestions for other useful information to be output welcome. Untested on
FreeBSD for now.
Sample output:
$ make system_info
CC version
==========
cc (GCC) 4.7.2 20121109 (Red Hat 4.7.2-8)
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
DPDK version
============
2.0.0-rc2
Git commit
==========
0431d322b80858b9efa1b43480be6d4ddccf4a66
Uname
=====
Linux 3.6.10-4.fc18.x86_64 #1 SMP Tue Dec 11 18:01:27 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Hugepages
=========
AnonHugePages: 102400 kB
HugePages_Total: 1024
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
============================================================
Core and Socket Information (as reported by '/proc/cpuinfo')
============================================================
cores = [0, 1, 2, 3, 4, 5, 6, 7]
sockets = [0, 1]
Socket 0 Socket 1
-------- --------
Core 0 [0, 16] [8, 24]
Core 1 [1, 17] [9, 25]
Core 2 [2, 18] [10, 26]
Core 3 [3, 19] [11, 27]
Core 4 [4, 20] [12, 28]
Core 5 [5, 21] [13, 29]
Core 6 [6, 22] [14, 30]
Core 7 [7, 23] [15, 31]
Network devices using DPDK-compatible driver
============================================
0000:84:00.0 '82599EB 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio unused=
0000:86:00.0 '82599EB 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio unused=
Network devices using kernel driver
===================================
0000:03:00.0 'RTL8111/8168 PCI Express Gigabit Ethernet controller' if=p260p1 drv=r8169 unused=igb_uio
0000:06:00.0 'I350 Gigabit Network Connection' if=em0 drv=igb unused=igb_uio
0000:06:00.1 'I350 Gigabit Network Connection' if=eth0 drv=igb unused=igb_uio
0000:81:00.0 '82599EB 10-Gigabit SFI/SFP+ Network Connection' if=p264p1 drv=ixgbe unused=igb_uio
0000:81:00.1 '82599EB 10-Gigabit SFI/SFP+ Network Connection' if=p264p2 drv=ixgbe unused=igb_uio
0000:84:00.1 '82599EB 10-Gigabit SFI/SFP+ Network Connection' if=p263p2 drv=ixgbe unused=igb_uio
0000:86:00.1 '82599EB 10-Gigabit SFI/SFP+ Network Connection' if=p262p2 drv=ixgbe unused=igb_uio
0000:88:00.0 '82599EB 10-Gigabit SFI/SFP+ Network Connection' if=p261p1 drv=ixgbe unused=igb_uio
0000:88:00.1 '82599EB 10-Gigabit SFI/SFP+ Network Connection' if=p261p2 drv=ixgbe unused=igb_uio
Other network devices
=====================
<none>
John McNamara (1):
mk: added make target to print out system info
mk/rte.sdkroot.mk | 33 +++++++++++++++++++++++++++++++++
1 file changed, 33 insertions(+)
--
1.8.1.4
next reply other threads:[~2015-03-24 14:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 14:52 John McNamara [this message]
2015-03-24 14:52 ` John McNamara
2015-03-24 17:00 ` Neil Horman
2015-03-25 15:06 ` Olivier MATZ
2015-03-25 15:22 ` Neil Horman
2015-03-25 15:42 ` Olivier MATZ
2015-03-25 17:22 ` Neil Horman
2015-03-25 17:42 ` Olivier MATZ
2015-03-25 17:57 ` Neil Horman
2015-03-25 18:11 ` Mcnamara, John
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=1427208779-16548-1-git-send-email-john.mcnamara@intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).