mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bart Van Assche <bart.vanassche@gmail.com>
To: linux-iscsi-target-dev@googlegroups.com
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Hannes Reinecke <hare@suse.de>,
	FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	Mike Christie <michaelc@cs.wisc.edu>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Ming Zhang <blackmagic02881@gmail.com>,
	Philipp Reisner <philipp.reisner@linbit.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Vladislav Bolkhovitin <vst@vlnb.net>
Subject: Re: [RFC PATCH 14/19] Target_Core_Mod SCSI MIBs
Date: Sun, 5 Apr 2009 09:03:09 +0200	[thread overview]
Message-ID: <e2e108260904050003r65a43c8cy84cf6f6e5a26bce7@mail.gmail.com> (raw)
In-Reply-To: <1238904131.4250.755.camel@haakon2.linux-iscsi.org>

On Sun, Apr 5, 2009 at 6:02 AM, Nicholas A. Bellinger
<nab@linux-iscsi.org> wrote:
>
> This patch adds support for SCSI MIBs through /proc/scsi_target/mib following RFC-4455.

According to the Net-SNMP documentation, an implementation of the
SCSI-MIB (RFC 4455) for Linux does not yet exist
(http://www.net-snmp.org/docs/mibs/). It would be great once
implementation of this MIB starts, the kernel would offer a
well-documented interface that allows to query the information this
MIB exports. This interface can then be implemented in any SCSI target
for which these statistics are available in the kernel (SCST, IET,
LIO). This will allow a single implementation of RFC 4455 in the
Net-SNMP project instead of multiple.

The patch you posted exports the statistics needed by RFC 4455 through
a procfs interface. Sorry, but IMHO this information should be
exported in other way than through procfs.

Bart.

      reply	other threads:[~2009-04-05  7:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-05  4:02 Nicholas A. Bellinger
2009-04-05  7:03 ` Bart Van Assche [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=e2e108260904050003r65a43c8cy84cf6f6e5a26bce7@mail.gmail.com \
    --to=bart.vanassche@gmail.com \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=akpm@linux-foundation.org \
    --cc=blackmagic02881@gmail.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=hare@suse.de \
    --cc=linux-iscsi-target-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=michaelc@cs.wisc.edu \
    --cc=philipp.reisner@linbit.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vst@vlnb.net \
    /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

all inboxes | Powered by JetHome®