* [LSF/MM TOPIC][LSF/MM ATTEND] LIO Target Synchronization with sysfs [resend]
@ 2016-02-27 16:19 Lee Duncan
2016-02-27 21:54 ` Nicholas A. Bellinger
0 siblings, 1 reply; 3+ messages in thread
From: Lee Duncan @ 2016-02-27 16:19 UTC (permalink / raw)
To: lsf-pc, linux-scsi
[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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [LSF/MM TOPIC][LSF/MM ATTEND] LIO Target Synchronization with sysfs [resend]
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
0 siblings, 1 reply; 3+ messages in thread
From: Nicholas A. Bellinger @ 2016-02-27 21:54 UTC (permalink / raw)
To: Lee Duncan; +Cc: lsf-pc, linux-scsi, target-devel, Mike Christie
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. ;)
> 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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [LSF/MM TOPIC][LSF/MM ATTEND] LIO Target Synchronization with sysfs [resend]
2016-02-27 21:54 ` Nicholas A. Bellinger
@ 2016-02-29 21:02 ` Lee Duncan
0 siblings, 0 replies; 3+ messages in thread
From: Lee Duncan @ 2016-02-29 21:02 UTC (permalink / raw)
To: Nicholas A. Bellinger; +Cc: lsf-pc, linux-scsi, target-devel, Mike Christie
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-02-29 21:07 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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.