From: Mark Lord <liml@rtr.ca>
To: IDE/ATA development list <linux-ide@vger.kernel.org>,
Tejun Heo <htejun@gmail.com>, Jeff Garzik <jgarzik@pobox.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Per ATA host sysfs attributes?
Date: Tue, 10 Mar 2009 16:12:11 -0400 [thread overview]
Message-ID: <49B6C99B.9030507@rtr.ca> (raw)
Guys,
I have added IRQ coalescing to sata_mv, but need a way to activate/tune it.
There are two simple parameters: an IRQ count threshold, and a time threshold.
Whenever either the count or the time threshold is exceeded,
the chip will generate an interrupt (assuming at least one completed event).
These two parameters are per-chip (actually, per group of four ports within the chip).
How can I export these for setting/query withing sysfs ?
It is all rather easy to create per-SCSI-host attrs in sysfs,
but I don't see any obvious way to do it per-chip.
Suggestions?
For now, I'm doing it with a module parameter,
but that's really rather stone-age in the sysfs era.
Thanks.
next reply other threads:[~2009-03-10 20:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 20:12 Mark Lord [this message]
2009-03-10 23:07 ` Per ATA host sysfs attributes? Jeff Garzik
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=49B6C99B.9030507@rtr.ca \
--to=liml@rtr.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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).