On Fri, Aug 16, 2019 at 11:59:04AM -0400, Douglas Gilbert wrote:
> On 2019-08-15 1:30 p.m., Bart Van Assche wrote:
> > On 8/13/19 9:19 PM, Douglas Gilbert wrote:
> > > Bart Van Assche hinted at a better API design but didn't present
> > > it. If he did, that would be the first time an alternate API
> > > design was presented for async usage in the 20 years that I have
> > > been associated with the driver.
> > 
> > I would like to start from the use cases instead of the implementation
> > of a new SG/IO interface. My employer uses the SG/IO interface for
> > controlling SMR and
> There is no "new" SG/IO interface. Linux has broken the ability of char
> drivers to safely use the read() and write() system calls. This
> adversely impacts the bsg and sg drivers. In response the following
> replacement mappings have been suggested in my first sg patchset:

I don't understand what you mean by "broken the ability of char drivers
to use the read() and write() system calls."

What changed, when did it change, what broke, and why can't we "fix" it
if it really is broken?


greg k-h

Reply via email to