From: "Thomas Maier" <balagi@justmail.de>
To: "Greg KH" <greg@kroah.com>, "Phillip Susi" <psusi@cfl.rr.com>
Cc: linux-kernel@vger.kernel.org, "petero2@telia.com" <petero2@telia.com>
Subject: Re: [PATCH] pktcdvd: added sysfs interface + bio write queue handling fix
Date: Sat, 09 Sep 2006 20:11:56 +0200 [thread overview]
Message-ID: <op.tfmh56j9iudtyh@master> (raw)
In-Reply-To: <20060908220129.GB20018@kroah.com>
Hello,
>> + write_queue_size (r) Contains the size of the bio write
>> + queue.
...
>> + mapped_to Symbolic link to mapped block device
>> + in the /sys/block tree.
>
> Shouldn't this whole thing be in /sys/class/ instead of /sys/block/ ?
Don't know. I thought, the pktcdvd is a block driver, so put
the control files into /sys/block ..
Is /sys/class better? If yes, where to put it?
> On Fri, Sep 08, 2006 at 05:40:11PM -0400, Phillip Susi wrote:
>> Greg KH wrote:
>> >On Fri, Sep 08, 2006 at 07:55:08PM +0200, Thomas Maier wrote:
>> >>+/sys/block/pktcdvd/<pktdevname>/packet/
>> >>+ statistic (r) Show device statistic. One line with
>> >>+ 5 values in following order:
>> >>+ packets-started
>> >>+ packets-end
>> >>+ written in kB
>> >>+ read gather in kB
>> >>+ read in kB
>> >
>> >Please no. One value per file is the sysfs rule.
>> >
>>
>> Except in cases like this where you want to read the status of the
>> device at a given point in time, and you can't do that unless you grab
>> all the values at once.
>
> Then don't use sysfs for that. And is something like this as critical
> to get that kind of information all in one atomic chunk? It seems
> merely to be informational.
The "statistic" and "info" files are only for information purpose.
Into /proc ? No. (i read somewhere /proc should only contain process
information in future)
In debugfs? Hmm, this files should be infos that users should be able
to read, no debug output.
Is it ok, if i split the "statistic" into 5 files, and put the "info"
into debugfs ?
-Thomas Maier
next prev parent reply other threads:[~2006-09-09 18:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 17:55 [PATCH] pktcdvd: added sysfs interface + bio write queue handling fix Thomas Maier
2006-09-08 18:53 ` Phillip Susi
2006-09-09 18:03 ` Thomas Maier
2006-09-08 21:00 ` Greg KH
2006-09-08 21:40 ` Phillip Susi
2006-09-08 22:01 ` Greg KH
2006-09-09 18:11 ` Thomas Maier [this message]
2006-09-09 21:30 ` Greg KH
2006-09-09 22:53 ` Kay Sievers
2006-09-10 19:33 ` Thomas Maier
2006-09-10 22:25 ` Kay Sievers
2006-09-10 19:27 ` Thomas Maier
2006-09-11 20:11 ` Thomas Maier
2006-09-11 20:07 ` [PATCH] class.c: added class_create_attrs() function Thomas Maier
-- strict thread matches above, loose matches on Subject: below --
2006-09-05 18:51 [PATCH] pktcdvd: added sysfs interface + bio write queue handling fix Thomas Maier
2006-09-03 18:20 Thomas Maier
2006-09-03 22:18 ` Randy.Dunlap
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=op.tfmh56j9iudtyh@master \
--to=balagi@justmail.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
--cc=psusi@cfl.rr.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.