From: Peter Hurley <peter@hurleysoftware.com>
To: linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: [RFC 0/4] Bluetooth: Expose HCI connections through debugfs
Date: Wed, 24 Aug 2011 10:04:49 -0400 [thread overview]
Message-ID: <1314194689.2219.13.camel@THOR> (raw)
This series adds a new debugfs file, "connections", to the "hciX" debugfs
directory and exposes the state and statistics of current hci connections.
The per-connection statistics will currently reflect 0 counts while the
tx scheduler is in flux. Also, I expect to add error counts to conditions
that should be flagged as errors, such as clamping the ACL and LE buffer
counts to their respective max values.
Lastly, track NULL ACL packets in these new per-connection statistics
rather than logging them.
Peter Hurley (4):
Bluetooth: Add LE link type for debugfs output
Bluetooth: Expose hci connections through debugfs
Bluetooth: Track per-connection stats
Bluetooth: l2cap: fix NULL ACL packet handling
include/net/bluetooth/hci_core.h | 12 +++++++
net/bluetooth/hci_sysfs.c | 65 ++++++++++++++++++++++++++++++++++++++
net/bluetooth/l2cap_core.c | 8 +++++
3 files changed, 85 insertions(+), 0 deletions(-)
--
1.7.4.1
reply other threads:[~2011-08-24 14:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1314194689.2219.13.camel@THOR \
--to=peter@hurleysoftware.com \
--cc=linux-bluetooth@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 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).