From: Ewan Milne <emilne@redhat.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-scsi@vger.kernel.org
Subject: [LSF/MM ATTEND] [LSF/MM TOPIC]
Date: Fri, 09 Jan 2015 11:14:08 -0500 [thread overview]
Message-ID: <1420820048.3891.156.camel@localhost.localdomain> (raw)
I'd like to attend LSF -- I am responsible for maintaining the SCSI
subsystem at Red Hat, and in addition to resolving issues for customers
and partners, I've been participating in upstream development for the
past couple of years. I have an extensive background in SCSI and OS
development, including 15 years of working with the Linux kernel.
I would also like to have a discussion at LSF/MM 2015 about how we could
better handle devices whose properties change after being probed. This
includes:
- READ CAPACITY data
- ALUA state
- EMC OWNED/UNOWNED state
- NOT READY state
Currently, when these properties change, we do not always handle it
very well (e.g. multipath stops using a path if the capacity changes,
even if it the only good path to the device...)
-Ewan Milne <emilne@redhat.com>
next reply other threads:[~2015-01-09 16:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-09 16:14 Ewan Milne [this message]
2015-01-10 13:41 ` [LSF/MM ATTEND] [LSF/MM TOPIC] Hannes Reinecke
2015-01-10 16:26 ` Matias Bjorling
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=1420820048.3891.156.camel@localhost.localdomain \
--to=emilne@redhat.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