Messages in this thread |  | | Date | Fri, 18 May 2001 13:54:41 +0200 | From | sebastien person <> | Subject | [newbie] timer in module |
| |
Hi,
I have a network module that need to regularly get data from network adaptater. But I don't know if it safe to do a loop with a timer in the module. e.g. I want to do something like that after ifconfig call :
while(1) { timer call() get data() // these datas are specific to device }
but I'm scared that will block the driver. I've no experience of a regularly call that let the hand to the module. My aim is to do a get data call every x seconds (x is variable).
Is it better to let an external program executing timer call and get data call via ioctl ?
In the case of a network module wich is able to send and receive data, whats happen if the driver is sollicited when he received or send data ? the tbusy bit is it designed to avoid this case ?
The module is it able to execute two different parts of the module code at the same time ? (receiving data and handle a higher layer request)
thanks for any comments.
sebastien person - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |