Hi,
thanks for the reply. From an application point of view, when a
socket is created it is non-blocking by default. If the application uses
ioctl or fcntl to set the socket to non-blocking mode, then all I was saying
was I don't see any indication in flags or msghdr->flags as to whether the
user wants to wait for the recv to complete or not. How is my recvmsg()
function in my implementation of the new address family supposed to
differentiate. I cannot see any reference to O_NONBLOCK or MSG_DONTWAIT in
the tcp_recvmsg() function.
Kevin
-----Original Message-----
From: Thunder from the hill [mailto:thunder@ngforever.de]
Sent: 08 July 2002 13:16
To: Kevin Curtis
Cc: linux-kernel@vger.kernel.org
Subject: Re: Implementing a sockets address family
Hi,
On Mon, 8 Jul 2002, Kevin Curtis wrote:
> 1) It seems that the only way you can tell if the socket is blocking or
> non-blocking is to looks at the flags or msghdr->flags on each function
> call. Is this the case? When the socket is set to non-blocking and a
call
> to the system recv() function is made, my recvmsg() function is called but
> neither the flags parameter nor the flags in the msghdr structure have any
> indication that the socket is non-blocking. What am I missing here?
non-blocking is a matter of behavior. It easily doesn't block.
The man page says
O_NONBLOCK or O_NDELAY
When possible, the file is opened in non-blocking
mode. Neither the open nor any subsequent opera-
tions on the file descriptor which is returned will
cause the calling process to wait. For the han-
dling of FIFOs (named pipes), see also fifo(4).
This mode need not have any effect on files other
than FIFOs.
So it shouldn't work outside FIFOs. However, have a look at net/ipv4/tcp.c
for more details.
Regards,
Thunder
-- (Use http://www.ebb.org/ungeek if you can't decode) ------BEGIN GEEK CODE BLOCK------ Version: 3.12 GCS/E/G/S/AT d- s++:-- a? C++$ ULAVHI++++$ P++$ L++++(+++++)$ E W-$ N--- o? K? w-- O- M V$ PS+ PE- Y- PGP+ t+ 5+ X+ R- !tv b++ DI? !D G e++++ h* r--- y- ------END GEEK CODE BLOCK------ - 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/
This archive was generated by hypermail 2b29 : Mon Jul 15 2002 - 22:00:13 EST