[Stgt-devel] [PATCH] add stgt_device_template example

FUJITA Tomonori fujita.tomonori at lab.ntt.co.jp
Sun Sep 11 14:09:59 CEST 2005

From: Mike Christie <michaelc at cs.wisc.edu>
Subject: Re: [Stgt-devel] [PATCH] add stgt_device_template example
Date: Fri, 09 Sep 2005 19:03:43 -0500

> >>>more generic message and callback(like STGT_UEVENT_SEND_MESSAGE) for
> >>>target driver specific tasks better?
> >>
> >>Yeah, maybe a generic event like that. Where if stgt doe not know how to 
> >>handle the event it passes it to the protocol or target driver or 
> >>transport. Or maybe it can flow downwards. For what we have now:
> >>
> >>STGT_UEVENT_SEND_MESSAGE->stgt (if not mine pass down) ->protocol (pass 
> >>down if not mine) ->target_driver (fail if not my message)
> >>
> >>I guess either way we need to add something on the event so we can 
> >>figure out who the event is supposed to be for. I ran into similar 
> >>troubles with passing things upwards (see the TODO I added to the 
> >>usr/netlink.c this morning).
> > 
> > 
> > How should we do this?
> > 
> > I think that user-space daemon need to know 'tid -> target driver' and
> > 'target driver -> protocol'. Are we adding something about them to
> > sysfs?
> I was trying to expose the protocol on the target sysfs stuff. Will do 
> this in a sec but it keeps locking up on me.

I sometimes see kernel panic though the code works in most cases. I'll
dig into the code later.

More information about the stgt mailing list