[Stgt-devel] supporting non-block devices

Pete Wyckoff pw
Mon Jan 22 20:01:32 CET 2007


fujita.tomonori at lab.ntt.co.jp wrote on Mon, 22 Jan 2007 16:23 +0900:
> From: Pete Wyckoff <pw at osc.edu>
> Subject: Re: [Stgt-devel] supporting non-block devices
> Date: Sun, 21 Jan 2007 11:50:12 -0500
> 
> > fujita.tomonori at lab.ntt.co.jp wrote on Sat, 20 Jan 2007 23:04 +0900:
> > > I plan to split the current scsi command code; spc.c and sbc.c. The
> > > device type specific code (sbc.c, osd.c, etc) can use functions in
> > > spc.c.
> > 
> > Sounds good.  I've broken out scsi_cmd_perform to do just SPC
> > commands, first.  Then it looks at target type and calls into SBC or
> > OSD to perform specific command sets.  This makes things pretty
> > modular for us.
> > 
> > Problem is, we are using our OSD emulator to actually process the
> > commands, not a chunk of hardware.  If you had OSD hardware, you
> > would presumably use something like LU_BS_RAW and the sg_bdt.
> > Instead I have an osdemu_bdt with a cmd_submit function that makes
> > calls out to this emulator library.  I don't want to put that in
> > stgt, as it's a mess and quite beyond the scope of stgt.
> 
> Well, I plan to implement a OSD emulator (osd.c).

That's great.  We'll be happy to use it.  In the mean time I'll send
the "generic" patches on stgt that are needed to understand OSD
commands, separating out sbc from spc as we talked about.

		-- Pete



More information about the stgt mailing list