All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [RFC] exposing the sdev_target in sysfs
Date: Sat, 4 Sep 2004 09:24:27 +0200	[thread overview]
Message-ID: <20040904072427.GA19656@suse.de> (raw)
In-Reply-To: <1094254851.1712.28.camel@mulgrave>

 On Fri, Sep 03, James Bottomley wrote:

> The aim of this patch is to give us somewhere to hang the per target
> timer that emulex needs.
> 
> However, it will break the current sysfs layout.  devices will now
> appear something like this:
> 
> lrwxrwxrwx  1 root root 0 Sep  3 18:31
> /sys/class/scsi_device/0:0:5:0/device ->
> ../../../devices/parisc8/parisc8:0/pci0000:00/0000:00:13.0/host0/target0:0:5/0:0:5:0
> 
> (note the extra target0:0:5 in there).
> 
> which may break some of the user land tools (although you're all using
> the scsi class interface to access your devices, aren't you? in which
> case you won't notice any problems).

I do something like this to get to the controller.
cd /sys/block/sda/device
cd `pwd -P`
cd ../..
But if target* will be a stable interface, its easy to change.

-- 
USB is for mice, FireWire is for men!

sUse lINUX ag, nÜRNBERG
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2004-09-04  7:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-03 23:40 [RFC] exposing the sdev_target in sysfs James Bottomley
2004-09-04  4:48 ` Mike Christie
2004-09-04 13:54   ` James Bottomley
2004-09-06  1:58     ` Matthew Wilcox
2004-09-06  2:05       ` James Bottomley
2004-09-04  7:24 ` Olaf Hering [this message]

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=20040904072427.GA19656@suse.de \
    --to=olh@suse.de \
    --cc=James.Bottomley@SteelEye.com \
    --cc=linux-scsi@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 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.