From: Joe Perches <joe@perches•com>
To: Gavin Shan <gwshan@linux•vnet.ibm.com>, netdev@vger•kernel.org
Cc: davem@davemloft•net
Subject: Re: [PATCH net-next 4/8] net/ncsi: Add debugging infrastructurre
Date: Wed, 12 Apr 2017 21:28:26 -0700 [thread overview]
Message-ID: <1492057706.28586.10.camel@perches.com> (raw)
In-Reply-To: <1492051600-26706-5-git-send-email-gwshan@linux.vnet.ibm.com>
On Thu, 2017-04-13 at 12:46 +1000, Gavin Shan wrote:
> This creates procfs directories as NCSI debugging infrastructure.
> With the patch applied, We will see below procfs directories. Every
> NCSI package and channel has one corresponding directory. Other than
> presenting the NCSI topology, No real function has been achieved
> through these procfs directories so far.
/proc is meant to be stable.
Why not use debugfs?
> /proc/ncsi/eth0
> /proc/ncsi/eth0/p0
> /proc/ncsi/eth0/p0/c0
> /proc/ncsi/eth0/p0/c1
next prev parent reply other threads:[~2017-04-13 4:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 2:46 [PATCH net-next 0/8] net/ncsi: Add debugging functionality Gavin Shan
2017-04-13 2:46 ` [PATCH net-next 1/8] net/ncsi: Disable HWA mode when no channels are found Gavin Shan
2017-04-13 2:46 ` [PATCH net-next 2/8] net/ncsi: Properly track channel monitor timer state Gavin Shan
2017-04-13 2:46 ` [PATCH net-next 3/8] net/ncsi: Enforce failover on link monitor timeout Gavin Shan
2017-04-13 2:46 ` [PATCH net-next 4/8] net/ncsi: Add debugging infrastructurre Gavin Shan
2017-04-13 4:28 ` Joe Perches [this message]
2017-04-13 5:11 ` Gavin Shan
2017-04-13 2:46 ` [PATCH net-next 5/8] net/ncsi: Dump NCSI packet statistics Gavin Shan
2017-04-13 2:46 ` [PATCH net-next 6/8] net/ncsi: Support NCSI packet generation Gavin Shan
2017-04-13 2:46 ` [PATCH net-next 7/8] net/ncsi: No error report on DP response to non-existing package Gavin Shan
2017-04-13 2:46 ` [PATCH net-next 8/8] net/ncsi: Fix length of GVI response packet Gavin Shan
2017-04-13 7:57 ` [PATCH net-next 0/8] net/ncsi: Add debugging functionality Gavin Shan
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=1492057706.28586.10.camel@perches.com \
--to=joe@perches$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=gwshan@linux$(echo .)vnet.ibm.com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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