public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Maier" <balagi@justmail.de>
To: "Kay Sievers" <kay.sievers@vrfy.org>, "Greg KH" <greg@kroah.com>
Cc: "Phillip Susi" <psusi@cfl.rr.com>,
	linux-kernel@vger.kernel.org,
	"petero2@telia.com" <petero2@telia.com>
Subject: Re: [PATCH] pktcdvd: added sysfs interface + bio write queue handling fix
Date: Sun, 10 Sep 2006 21:33:16 +0200	[thread overview]
Message-ID: <op.tfoglqsiiudtyh@master> (raw)
In-Reply-To: <1157842406.7592.12.camel@pim.off.vrfy.org>

Hello,

> Is this always device specific, or also driver global information? Is
> pktcdvd always on a block device? Maybe you just want them to be a group
> of attributes in the block device directory where they belong to, like:
>   /sys/block/sr0/pktcdvd/info
>   /sys/block/sr0/pktcdvd/write_queue_size
>   /sys/block/sr0/pktcdvd/...
>
> Does that make sense? We should avoid messing around with symlinks
> pointing to other devices, if not absolutely needed. We should also not
> create a new device type, just for adding properties to an existing one,
> especially if there is not some kind of "device stacking". The
> "mapped_to" link to the parent device looks like a wild hack to me, we
> should avoid.

The pktcdvd driver creates new block devices using a "struct gendisk"
that creates the /sys/block/pktcdvd[0-7]/ entries (alloc_disk() -> add_disk()).

Since the files like write_queue_size are per pktcdvd device and belong to
this device, they should be below the /sys/block/pktcdvd[0-7]/ directory,
not below the e.g. /sys/block/sr0/ .

The pktcdvd driver can only be mapped to block devices, as i know.

-Thomas Maier


  reply	other threads:[~2006-09-10 19:25 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
2006-09-09 21:30         ` Greg KH
2006-09-09 22:53           ` Kay Sievers
2006-09-10 19:33             ` Thomas Maier [this message]
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.tfoglqsiiudtyh@master \
    --to=balagi@justmail.de \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox