From: Lee Duncan <lduncan@suse.com>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: lsf-pc@lists.linux-foundation.org,
linux-scsi <linux-scsi@vger.kernel.org>,
target-devel <target-devel@vger.kernel.org>,
Mike Christie <michaelc@cs.wisc.edu>
Subject: Re: [LSF/MM TOPIC][LSF/MM ATTEND] LIO Target Synchronization with sysfs [resend]
Date: Mon, 29 Feb 2016 13:02:41 -0800 [thread overview]
Message-ID: <56D4B1F1.6040600@suse.com> (raw)
In-Reply-To: <1456610092.1750.34.camel@haakon3.risingtidesystems.com>
On 02/27/2016 01:54 PM, Nicholas A. Bellinger wrote:
> On Sat, 2016-02-27 at 08:19 -0800, Lee Duncan wrote:
>> [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.
>>
>
> I assume you mean configfs, and not sysfs. ;)
Apologies. Yes.
>
>> As for other topics:
>>
>> As one of the maintainers of LIO at SUSE, I'd dearly love to see our
>> iSCSI targets merged.
>>
>
> You're talking about Mike's (CC'ed) original target_core_rbd.c driver,
> right..?
>
> He's been working on porting the PR related changes to a generic
> interface that can be consumed by multiple backend using
> target_core_iblock.c.
>
Actually, no. I'm aware of that work because one of the groups I'm in is
working in that area. And that is of interest to me to.
But I meant the scst/lio merge, one of the proposed LSF/MM topics.
--
Lee Duncan
prev parent reply other threads:[~2016-02-29 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 16:19 [LSF/MM TOPIC][LSF/MM ATTEND] LIO Target Synchronization with sysfs [resend] Lee Duncan
2016-02-27 21:54 ` Nicholas A. Bellinger
2016-02-29 21:02 ` Lee Duncan [this message]
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=56D4B1F1.6040600@suse.com \
--to=lduncan@suse.com \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=michaelc@cs.wisc.edu \
--cc=nab@linux-iscsi.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.