From: Mike Christie <mchristi@redhat.com>
To: target-devel@vger.kernel.org
Subject: [RFC PATCH 00/15] target: export session info
Date: Sun, 15 Jul 2018 23:16:16 +0000 [thread overview]
Message-ID: <1531696591-8558-1-git-send-email-mchristi@redhat.com> (raw)
Currently, session info is in 3 places:
1. iscsi has the info file under initiator acls.
2. In the tpg dir iscsi and qla have the dynamic sessions.
3. Some lun stat files return some initiator info.
The problem with these is for:
1 and 3 - They only display 1 session's info per target port.
In multipath and HA setups you will have multiple initiator ports
connected to each target port, so for iscsi the isid will be different
for each session.
2 - We only get the initiator name. For iscsi we want the isid. Also
if we have a lot of sessions we are limited by the PAGE_SIZE file limit.
To handle all these issues these patches add session info under
/sys/kernel/config/target/iscsi/$target_name/tpgt_$N/sessions
This only a RFC right now. There is still a bug in the iscsi code
where if configfs registration fails we have to cleanup the
session.
reply other threads:[~2018-07-15 23:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1531696591-8558-1-git-send-email-mchristi@redhat.com \
--to=mchristi@redhat.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;
as well as URLs for NNTP newsgroup(s).