public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Thomas Maier <balagi@justmail.de>
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: Fri, 8 Sep 2006 14:00:42 -0700	[thread overview]
Message-ID: <20060908210042.GA6877@kroah.com> (raw)
In-Reply-To: <op.tfkmp60biudtyh@master>

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.

> +    reset_statistic   (w)  Write any value to it to reset
> +                           pktcdvd device statistic values, like
> +                           bytes read/written.
> +
> +    info              (r)  Lots of user readable driver statistics
> +                           and infos. Multiple lines!

Again, no.  Put it in debugfs if you want multiple lines.

> +    write_queue_size  (r)  Contains the size of the bio write
> +                           queue.
> +
> +    write_congestion_off (rw) If bio write queue size is below
> +                              this mark, accept new bio requests
> +                              from the block layer.
> +
> +    write_congestion_on  (rw) If bio write queue size is higher
> +                              as this mark, do no longer accept
> +                              bio write requests from the block
> +                              layer and wait till the pktcdvd
> +                              device has processed enough bio's
> +                              so that bio write queue size is
> +                              below congestion off mark.
> +
> +    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/ ?

thanks,

greg k-h

  parent reply	other threads:[~2006-09-08 21:00 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 [this message]
2006-09-08 21:40   ` Phillip Susi
2006-09-08 22:01     ` Greg KH
2006-09-09 18:11       ` Thomas Maier
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=20060908210042.GA6877@kroah.com \
    --to=greg@kroah.com \
    --cc=balagi@justmail.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petero2@telia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox