From: Himanshu Madhani <himanshu.madhani@qlogic.com>
To: Bart Van Assche <bart.vanassche@sandisk.com>,
"target-devel@vger.kernel.org" <target-devel@vger.kernel.org>,
"nab@linux-iscsi.org" <nab@linux-iscsi.org>
Cc: Giridhar Malavali <giridhar.malavali@qlogic.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
Quinn Tran <quinn.tran@qlogic.com>
Subject: Re: [PATCH 3/4] qla2xxx: Add DebugFS node for target sess list.
Date: Fri, 5 Feb 2016 17:26:01 +0000 [thread overview]
Message-ID: <D2DA1ACE.D6B81%himanshu.madhani@qlogic.com> (raw)
In-Reply-To: <56B39597.2020405@sandisk.com>
Hi Bart,
On 2/4/16, 10:16 AM, "Bart Van Assche" <bart.vanassche@sandisk.com> wrote:
>On 02/04/2016 08:45 AM, Himanshu Madhani wrote:
>> From: Quinn Tran <quinn.tran@qlogic.com>
>>
>> #cat /sys/kernel/debug/qla2xxx/qla2xxx_31/tgt_sess
>> qla2xxx_31
>> Port ID Port Name Handle
>> ff:fc:01 21:fd:00:05:33:c7:ec:16 0
>> 01:0e:00 21:00:00:24:ff:7b:8a:e4 1
>> 01:0f:00 21:00:00:24:ff:7b:8a:e5 2
>> ....
>
>Hello Quinn and Himanshu,
>
>The above information is not only useful to people who are debugging the
>QLogic target driver but also to end users who want to check which
>initiator ports have already logged in to a target port. Hence my
>proposal to move this information from debugfs to another location (e.g.
>configfs or sysfs). Users of other target drivers are probably also
>interested in seeing which sessions are active. How about adding the
>functionality for reporting session information per target port in the
>LIO core in such a way that some attributes are available for all target
>drivers (e.g. initiator port name, SCSI command statistics) and such
>that target drivers can define additional attributes to exported for
>each session (e.g. port ID, handle, ...).
We had initially implemented this as a sysfs hook, but knowing that sysfs
is not encouraged, we decided to put this information via debugfs. Would it
make more sense if we send a sysfs patch?
>
>Thanks,
>
>Bart.
Thanks,
- Himanshu
next prev parent reply other threads:[~2016-02-05 17:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 16:45 [PATCH 0/4] qla2xxx: Patches for target-pending branch Himanshu Madhani
2016-02-04 16:45 ` [PATCH 1/4] qla2xxx: Fix stale pointer access Himanshu Madhani
2016-02-04 16:45 ` [PATCH 2/4] qla2xxx: Use ATIO type to send correct tmr response Himanshu Madhani
2016-02-04 16:45 ` [PATCH 3/4] qla2xxx: Add DebugFS node for target sess list Himanshu Madhani
2016-02-04 18:16 ` Bart Van Assche
2016-02-05 17:26 ` Himanshu Madhani [this message]
2016-02-05 20:00 ` Bart Van Assche
2016-02-05 20:17 ` Giridhar Malavali
2016-02-07 4:44 ` Nicholas A. Bellinger
2016-02-07 4:40 ` Nicholas A. Bellinger
2016-02-07 5:00 ` Nicholas A. Bellinger
2016-02-09 18:01 ` Himanshu Madhani
2016-02-08 17:43 ` Himanshu Madhani
2016-02-09 5:49 ` Nicholas A. Bellinger
2016-02-09 21:30 ` Himanshu Madhani
2016-02-04 16:45 ` [PATCH 4/4] qla2xxx: Add DebugFS node to show irq vector's cpuid Himanshu Madhani
2016-02-04 18:20 ` Bart Van Assche
2016-02-05 18:49 ` Quinn Tran
2016-02-05 19:42 ` Bart Van Assche
2016-02-05 21:52 ` Quinn Tran
2016-02-07 4:31 ` [PATCH 0/4] qla2xxx: Patches for target-pending branch Nicholas A. Bellinger
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=D2DA1ACE.D6B81%himanshu.madhani@qlogic.com \
--to=himanshu.madhani@qlogic.com \
--cc=bart.vanassche@sandisk.com \
--cc=giridhar.malavali@qlogic.com \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=quinn.tran@qlogic.com \
--cc=target-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox