[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [RFC PATCH] blkif.h: document scsi/0x12/0x83 node
Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] [RFC PATCH] blkif.h: document scsi/0x12/0x83 node"): > > I don't think this is a sterile academic conversation which would (if > > satisfactorily answered) have no real implications. Rather, if we > > understood the use case properly, there would probably be implications > > for whether how this functionality ought to be exposed via the libxl > > API; whether blkfront should consume this information by default; and > > so on. > > Lets take one step back. > > What is the problem with documenting an existing use-case in blkif.h? > > Regardless of whether it is viewed "legacy" by some folks and by others > drivers it is still in use? Firstly, if you want to document it then the documentation needs to explain what the semantics are supposed to be. At the moment I'm not sure I see a correct and useful set of semantics. I had a go at writing something but several of the things I wrote in it seem to have been contradicted by comments from Bob Liu and others. It is difficult to write a suitable document. Ideally the document would give an example use case. But it appears that the only use case is super secret! Secondly, apparently this is not regarded as deprecated. Bob Liu says he plans to add support for it to blkfront. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |