kqueue/kevent support in scsi device drivers

2003-05-30 Thread Jayasheela Bhat
Hi All,
 
At present, kevent is supported for vnode, fifos, pipes and sockets, I believe. 
I would like to use kevent notification in scsi devices. But the drivers scsi_xx.c do 
not support it. Whether I can implement it in scsi device driver using KNOTE? 
I was going through tty.c where KNOTE is used. struct 'tty' has the support for it. 
The same is not available in struct 'disk'.  
Could anyone tell me whether it is possible to implement it and how??
 
Thanks,
Jaya
 

Catch all the cricket action. Download Yahoo! Score tracker
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: kqueue/kevent support in scsi device drivers

2003-06-12 Thread Jayasheela Bhat
yeah, I would like to implement it in scsi_target driver. I am using scsi HBA in 
target to emulate as a sequential device. My userland application needs to be notified 
of some events taking place in scsi_target driver.
 
Could you pls suggest me the best approach for this??
 
Thanks, 
Jaya

Valentin Nechayev <[EMAIL PROTECTED]> wrote:
Fri, May 30, 2003 at 12:14:50, jaya_bhat100 (Jayasheela Bhat) wrote about 
"kqueue/kevent support in scsi device drivers": 

JB> At present, kevent is supported for vnode, fifos, pipes and sockets, I believe. 
JB> I would like to use kevent notification in scsi devices. But the drivers scsi_xx.c 
do not support it. Whether I can implement it in scsi device driver using KNOTE? 
JB> I was going through tty.c where KNOTE is used. struct 'tty' has the support for 
it. The same is not available in struct 'disk'. 
JB> Could anyone tell me whether it is possible to implement it and how??

What is the aim to do it? tty, sockets, pipes, fifos are sequential devices
with data pushing to it. Disks are random access devices, this is the main
reason why disk/filesystem read() can't be nonblocking by itself: there
are two different operations in them - 1) process says to kernel what it
want read, 2) kernel returns data. (And similarly for write().)
To read from random access devices, AIO API was created (aio_read(),
aio_write(), etc.), and it doesn't require your explicit KNOTE adding:
it already supports EVFILT_AIO and SIGEV_KEVENT.

If you can access something at SCSI subsystem as sequential device,
let you go. But, it's better to implement KNOTE in driver of this device
itself, not common SCSI layer, which is too complicated to allow it.


-netch-

Catch all the cricket action. Download Yahoo! Score tracker
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Driver to Driver Communication

2003-08-14 Thread Jayasheela Bhat

Hi All,

Could anybody help me to know how a driver to driver communication is done in FreeBSD 
? 
My exact problem is something like this. In the current implementation of scsi_target 
mode driver, there is a associated userland application polling the target device and 
data is read from target device to user space and then written to a file. In stead, I 
want to do it in the scsi_target driver itself such that all I/O queues are redirected 
to a disk device. For this purpose, How can I interface with the scsi disk driver i.e. 
scsi_da.c from the scsi_target driver? 

Thanks & Regards,

Jaya



SMS using the Yahoo! Messenger;Download latest version.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"