Date: Mon, 5 Sep 2005 17:53:28 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Luigi Rizzo <rizzo@icir.org> Cc: cvs-src@FreeBSD.org, Gleb Smirnoff <glebius@FreeBSD.org>, cvs-all@FreeBSD.org, src-committers@FreeBSD.org Subject: Re: cvs commit: src/sys/kern kern_poll.c Message-ID: <20050905175127.L88940@fledge.watson.org> In-Reply-To: <20050905094341.A23343@xorpc.icir.org> References: <200509051602.j85G2Bpo090258@repoman.freebsd.org> <20050905094341.A23343@xorpc.icir.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 5 Sep 2005, Luigi Rizzo wrote: > Also, what is the overall design - do you want to support multiple > polling loops running concurrently (netisr_poll, one poll_idle per CPU, > and possibly the poll_in_trap) ? Issues to be particularly careful about will be priority inversion and ordering. With a single thread associated with any given interface, the inversion problem might exist, but not the ordering issue, but if more than one thread may process a particular interface, there are potentially also ordering issues. It's been proposed that at the EuroBSDCon developer summit, we set aside a chunk of time to talk about the future structuring of polling -- in particular, how we can broaden the scope of the polling infrastructure to allow non-network device drivers also have their handlers run from a polled environment. A couple of hours of white board session would probably be quite useful, since I think there's a lot to discuss here. Robert N M Watson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050905175127.L88940>