Re: ioctls, etc. (was Re: [PATCH 1/4] sas: add flag for locally attached PHYs)

[Jeff Garzik <jgarzik@pobox.com>]

Luben Tuikov wrote:
> On 10/20/05 20:46, Jeff Garzik wrote:
> 
>>Consider what an ioctl is, overall:  a domain-specific "do this 
>>operation" interface.  Which, further, is nothing but a wrapping of a 
>>"send message" + "receive response" interface.  There are several ways 
>>to do this in Linux:
>>
>>* block driver.  a block driver is nothing but a message queue.  This is 
> 
> 
> Not quite.  This maybe the way it operates, but it is called "block"
> for a reason.

This illustrates you fundamentally don't understand a lot of Linux, and 
SCSI too.

Several non-blkdev device classes (Christoph listed them) use block 
layer request_queue for command transit, as does SG_IO and /dev/sg.


>>why James has suggested implementing SMP as a block driver.  People get 
>>stuck into thinking "block driver == block device", which is wrong.  The 
>>Linux block layer is nothing but a message queueing interface.
> 
> 
> Now, just because James suggested implementing the SMP service as a block
> device you think this is the right thing to do?

I very clearly said I don't know the best answer.  Perhaps you need to 
re-read the quoted email?


> How about this: Why not as a char device?

I covered that in the quoted email.


> At least MS isn't suffering from the "no to specs" syndrome which
> the Linux community seems to be suffering...

We have plenty of specs.  It's called source code.

You don't understand the Linux development process (think its more 
political than technical) and you don't understand even what a block 
driver is, and you wonder why you have difficulty getting code into the 
kernel?

	Jeff