From: James Smart <James.Smart@Emulex.Com>
To: James.Smart@Emulex.Com
Cc: Mike Christie <michaelc@cs.wisc.edu>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] [REPOST] SCSI and FC Transport: add netlink support for posting of transport events
Date: Sun, 20 Aug 2006 09:30:06 -0400 [thread overview]
Message-ID: <44E863DE.7040802@emulex.com> (raw)
In-Reply-To: <44E8605B.1070102@emulex.com>
After thinking about this a little more - most vendor apps will have
already perused sysfs to find the adapters they care about. If so, they
already have the host no to vendor mapping. So why pass the vendor id ?
It's for the scenario in which someone is logging event messages for
later, and may not have the sysfs tree present. Hmmm... implies the
logging app, to be really useful, should also log the syfs to host_no
relation as part of it's start up.
It's a good question/discussion, but it hasn't changed my position:
- for generic/well-known transport events, no vendor id is needed
- for vendor-specific events, supply vendor id.
-- james s
next prev parent reply other threads:[~2006-08-20 13:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 21:30 [PATCH] [REPOST] SCSI and FC Transport: add netlink support for posting of transport events James Smart
2006-08-19 4:11 ` Mike Christie
2006-08-19 11:56 ` James Smart
2006-08-20 2:26 ` Mike Christie
2006-08-20 13:15 ` James Smart
2006-08-20 13:30 ` James Smart [this message]
2006-08-20 22:35 ` Mike Christie
2006-08-20 22:46 ` Mike Christie
2006-08-20 23:01 ` Mike Christie
2006-08-21 0:03 ` Mike Christie
2006-08-30 17:40 ` James Bottomley
2006-08-30 17:51 ` James Smart
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=44E863DE.7040802@emulex.com \
--to=james.smart@emulex.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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.