From: lduncan@suse.com
To: lsf-pc@lists.linux-foundation.org
Cc: linux-scsi@vger.kernel.org, linux-block@vger.kernel.org
Subject: [LSF/MM/BPF Topic][LSF/MM/BPF Attend] iscsi issue of scale with MNoT
Date: Thu, 17 Feb 2022 10:19:07 -0800 (PST) [thread overview]
Message-ID: <20220217181907.A2460E9317@localhost> (raw)
[RESEND -- apologies if you see this more than once]
The iSCSI protocol continues to be used in Linux, but some of the
users push the system past its normal limits. And using multipath just
exacerbates that problem (usually doubling the number of sessions).
I'd like to gather some numbers for open-iscsi (the standard Linux
iSCSI initiator) and the kernel target code (i.e. LIO/targetcli) on
what happens when there are MNoT -- massive numbers of targets.
"Massive" in my case, will be relative, since I don't have access to
a supercomputer, but I believe it will not be too hard to start
pushing the system too far. For example, a recent user problem found
that even at 2000 sessions using multipath, the system takes about 80
seconds to switch paths. Each switch takes 80ms (and they are
currently serialized), but when you multiply that by 1000 it adds up.
For the initiator, I've long suspected some parts of the code were not
designed for scale, so this might give me a chance to find and
possibly address some of these issues.
--
Lee Duncan
next reply other threads:[~2022-02-17 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 18:19 lduncan [this message]
2022-03-01 23:34 ` [LSF/MM/BPF Topic][LSF/MM/BPF Attend] iscsi issue of scale with MNoT Khazhy Kumykov
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=20220217181907.A2460E9317@localhost \
--to=lduncan@suse.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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