Date: Sat, 10 Apr 1999 23:17:16 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: peter@spinner.netplex.com.au (Peter Wemm) Cc: tlambert@primenet.com, barney@databus.com, smp@FreeBSD.ORG, dot@dotat.at Subject: Re: concurrent select()s on listen socket broken under SMP Message-ID: <199904102317.QAA25435@usr08.primenet.com> In-Reply-To: <19990410123901.44DD21F4D@spinner.netplex.com.au> from "Peter Wemm" at Apr 10, 99 08:38:58 pm
next in thread | previous in thread | raw e-mail | index | archive | help
I'll probably respond in detail to other issues later; right now, I just want to make a quick point... > A list/queue/whatever would be one way, but this requires a driver API > redesign in a big way. > > At the moment, the drivers manage the select event wakeups. A process > calls select/poll(), and this eventually translates into a selscan() call > which ends up calling the driver d_select() (now d_poll) entry point. If > the event is not presently active, selrecord() is used to log the event in > the *driver*'s private selinfo struct that it provides for that event. I think that we should look at UDI as an opportunity for redesign in this area: http://www.sco.com/udi/ Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199904102317.QAA25435>