All of lore.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-scsi@vger.kernel.org
Subject: Re: State of sg_proc_host_info and sg_proc_hoststrs_info
Date: Sun, 10 Nov 2002 22:00:04 +1100	[thread overview]
Message-ID: <3DCE3C34.3090802@torque.net> (raw)
In-Reply-To: 20021110035104.A31903@lst.de

Christoph Hellwig wrote:
> Hi Douglas,
> 
> do you know of any users that rely on these functions or rather the
> /proc file generated by them?  I plan to rationalize and properly
> lock down handling of the scsi host list, and I'd prefer to have
> the replacement for scsi_host_get_next() not export to module (sg
> is the only user currently).

That means dropping this information from sg:

$ cd /proc/scsi/sg/
$ cat host_hdr hosts
uid     busy    cpl     scatg   isa     emul
0       0       3       64      0       0
0       0       5       256     0       1

$ cat host_strs
scsi_debug, Version: 1.64 (20021109), num_devs=9, dev_size_mb=8
SCSI host adapter emulation for IDE ATAPI devices

I put it in in lk 2.4 because the information was
hard to find from the user space. For example a
host (HBA) with no live devices on it was almost
invisible to the user space in lk 2.2

The "host_strs" stuff is available via an ioctl
in the mid-level and is really per driver rather
than per host. Hopefully sysfs will provide similar
information. Will you leave the
/proc/scsi/<driver_name>/host_no information?

The "hosts" stuff (i.e. the numeric data) was useful
to me (at least). The "uid" column was a mistake but
the rest was informative. Most of the data is static
(apart from "busy").

So take it out (along with host_hdr) if it makes life
easier for you.

Doug Gilbert




      reply	other threads:[~2002-11-10 11:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-10  2:51 State of sg_proc_host_info and sg_proc_hoststrs_info Christoph Hellwig
2002-11-10 11:00 ` Douglas Gilbert [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=3DCE3C34.3090802@torque.net \
    --to=dougg@torque.net \
    --cc=hch@lst.de \
    --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.