Hello,
I'm absolutely green when it comes to Linux kernel development, and so
working on a school project to port a TCP/IP-based service into the kernel
has been quite challenging (but also intesting)! Currently, I'm absolutely
mystified regarding how the "wait queue" subsystem works. I've been
reading the code, and usually that combined with an example is enough,
but not this time.
I searched the linux-kernel archives, and found a message from Mr. Timur
Tabi ([email protected]). In October, he asked for an explanation of
'wait_queue_head_t' vs. 'wait_queue_t'. I'm confused on this (as well as
several other points), but unfortunately, I didn't see any response to Mr.
Tabi. So, I thought I'd try fashioning my own message.
The kHTTPd source is in many ways similar to what we are trying to
accomplish. Basically, we are trying to implement select() in the kernel
-- we have a bunch of sockets, and we want to return when one of them has
data. We have code that performs all of the necessary checks, but the
whole "going to sleep until data arrives" aspect is the stumper.
I have managed to draw the following skeleton from the kHTTPd source
(main.c):
wait_queue_head_t dummyWQ;
init_waitqueue_head (&dummyWQ);
DECLARE_WAITQUEUE (local_wait);
add_wait_queue_exclusive (socket->sk->sleep, &local_wait);
set_current_state (TASK_INTERRUPTIBLE|TASK_EXCLUSIVE);
while (we don't need to stop) {
if nothing on socket
interruptible_sleep_on_timeout (&dummyWQ, timeout);
else
handle socket data
}
remove_wait_queue (sock->sk->sleep, &local_wait);
>From the structure of the kHTTPd code, it appears as if the call to
'interruptible_sleep_on_timeout()' will return when either data arrives on
one of the sockets that kHTTPd controls, or if the timeout transpires.
However, I cannot see how this can be so. It appears as if the 'dummyWQ'
and 'local_wait' queue are entirely *separate*. I can see how the socket
is tied to the 'local_wait' (via add_wait_queue_exclusive()), but I do not
comprehend how 'interruptible_sleep_on_timeout() knows anything about any
sockets.
Any assistance that could be provided (explaining the wait_queue function
calls, a pointer to some documentation, etc.) would be *sincerely*
appreciated. Please CC: all responses to me directly, since I am not
subscribed to the list.
TIA,
--Andy Reitz.
--
Andy Reitz <[email protected]> (217) 244-3862
Research Assistant, CCSO http://www.uiuc.edu/ph/www/areitz
[email protected] said:
> I have managed to draw the following skeleton from the kHTTPd source
Don't look at that code. It uses sleep_on(), therefore is probably broken.
--
dwmw2
Andrew Reitz wrote:
>
> Hello,
>
> I'm absolutely green when it comes to Linux kernel development, and so
> working on a school project to port a TCP/IP-based service into the kernel
> has been quite challenging (but also intesting)! Currently, I'm absolutely
> mystified regarding how the "wait queue" subsystem works. I've been
> reading the code, and usually that combined with an example is enough,
> but not this time.
Andy,
Go get "Linux Device Drivers" by Rubini (O'Reilly). It talks about that
and a lot of other useful stuff. Some of it is a bit dated by
development in 2.2 & 2.[34], but it'll help a lot.
Good luck,
Eli
--------------------. "To the systems programmer, users and applications
Eli Carter | serve only to provide a test load."
[email protected] `---------------------------------- (random fortune)