From: Lee Duncan <lduncan@suse.com>
To: lsf-pc@lists.linux-foundation.org,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: [LSF/MM TOPIC][LSF/MM ATTEND] LIO Target Synchronization with sysfs [resend]
Date: Sat, 27 Feb 2016 08:19:08 -0800 [thread overview]
Message-ID: <56D1CC7C.7050609@suse.com> (raw)
[Apologies for the resend.]
I would like to attend LSF/MM this year. I would like to discuss
problems I've had dealing with LIO targets and their inherent
asynchronicity in sysfs. I believe that with judicious use of kernel
events we can help user space handle target changes more cleanly.
As for other topics:
As one of the maintainers of LIO at SUSE, I'd dearly love to see our
iSCSI targets merged.
I also would love to see multipath work in a sane way, and *with* the
SCSI subsystem, not on top of it, so I'd like to join that discussion.
--
Lee Duncan
next reply other threads:[~2016-02-27 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 16:19 Lee Duncan [this message]
2016-02-27 21:54 ` [LSF/MM TOPIC][LSF/MM ATTEND] LIO Target Synchronization with sysfs [resend] Nicholas A. Bellinger
2016-02-29 21:02 ` Lee Duncan
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=56D1CC7C.7050609@suse.com \
--to=lduncan@suse.com \
--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