Re: UDP/IP Problem

• To: Voon-Li Chung <vlchung@cs.uwa.edu.au>
• Subject: Re: UDP/IP Problem
• From: Alastair Reid <reid@cs.utah.edu>
• Date: Tue, 07 Dec 1999 23:53:53 -0700
• cc: Alastair Reid <reid@cs.utah.edu>, oskit-users@cs.utah.edu
• In-reply-to: Your message of "Wed, 08 Dec 1999 14:18:36 +0800." <Pine.LNX.4.10.9912081415480.14543-100000@quokka.cs.uwa.oz.au>
• Sender: owner-oskit-users@fast.cs.utah.edu

> The idea behind using setsockopt to adjust the time before an
> EWOULDBLOCK is generated was so that the thread executing the code
> would only block for a specific amount of time (I'm using the BSD
> style, involving integer-based socket descriptors).

I'm a little confused about what your code is doing.
Is the relevant code short enough that you can send us it?

> Not knowing much about how that particular area of the oskit works
> (I'm using the original 0.97), do you know if is_softnetpending
> supposed to be cleared if it returns an EWOULDBLOCK?

Sadly, I don't know the socket-related code very well myself.  In
particular, I've no idea if users of client can accidentally find
themselves running in the bottom-half.  That (and you calling a
blocking function) would be the most obvious way for that assertion to
fail.

Hopefully someone who really knows this code can answer it properly in
the morning.


Goodnight,

Alastair

• Re: UDP/IP Problem
• From: Voon-Li Chung <vlchung@cs.uwa.edu.au>

• Prev: Re: UDP/IP Problem
• Next: Re: UDP/IP Problem
• Index(es):
  • Main
  • Thread