From: "Sean Hefty" <sean.hefty@intel.com>
To: "'Greg KH'" <greg@kroah.com>
Cc: <rolandd@cisco.com>, <hal.rosenstock@gmail.com>,
<general@lists.openfabrics.org>, <linux-kernel@vger.kernel.org>
Subject: RE: question about drivers/infiniband/core/cm.c's kobject usage
Date: Thu, 22 May 2008 14:47:51 -0700 [thread overview]
Message-ID: <000501c8bc55$7c2dd680$ec248686@amr.corp.intel.com> (raw)
In-Reply-To: <20080522203403.GA27263@kroah.com>
>So I was curious, was this done on purpose? If so, why? If not, any
>objection to me switching it over to be using struct device properly?
It's entirely possible I have this wrong, but the intent is to export some
infiniband communication management message counters and relate them to the
corresponding ib_device/port. For example:
/sys/class/infiniband_cm/<device name>/<port number>/<counter group>/<counter>
(E.g. /sys/class/infiniband_cm/mthca0/1/cm_tx_msgs/req)
If there's a better way to handle this, I have no objection to changing it.
- Sean
next prev parent reply other threads:[~2008-05-22 21:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 20:34 question about drivers/infiniband/core/cm.c's kobject usage Greg KH
2008-05-22 21:47 ` Sean Hefty [this message]
2008-05-22 21:58 ` Greg KH
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='000501c8bc55$7c2dd680$ec248686@amr.corp.intel.com' \
--to=sean.hefty@intel.com \
--cc=general@lists.openfabrics.org \
--cc=greg@kroah.com \
--cc=hal.rosenstock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rolandd@cisco.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 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.