From owner-freebsd-arch Wed Jan 15 2: 6:29 2003 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C8BF337B401 for ; Wed, 15 Jan 2003 02:06:28 -0800 (PST) Received: from park.rambler.ru (park.rambler.ru [81.19.64.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 182CB43F13 for ; Wed, 15 Jan 2003 02:06:27 -0800 (PST) (envelope-from is@rambler-co.ru) Received: from is.park.rambler.ru (is.park.rambler.ru [81.19.64.102]) by park.rambler.ru (8.12.6/8.12.6) with ESMTP id h0FA6FQB053434; Wed, 15 Jan 2003 13:06:15 +0300 (MSK) Date: Wed, 15 Jan 2003 13:06:15 +0300 (MSK) From: Igor Sysoev X-Sender: is@is To: Matthew Dillon Cc: arch@FreeBSD.ORG Subject: Re: getsysfd() patch #1 (Re: Virtual memory question) In-Reply-To: <200301150316.h0F3GIe8005442@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 14 Jan 2003, Matthew Dillon wrote: > Communication between kernel and userland could use a VM Object like > this... consider kqueue and AIO operation that does not require copying > to and from userspace. Instead you implement a message queue with a > shared VM object and tell the kernel to go. This would allow a bunch of > I/O and/or kqueue requests to be collected together and then initiated > with a single system call, and events could be reported back on a > different VM Object. > > (just brainstorming). Last Linux kernels introduced epoll (small subset of kqueue with EV_CLEAR flag): http://www.xmailserver.org/linux-patches/nio-improve.html It uses mmap()ed area to get event array. Igor Sysoev http://sysoev.ru/en/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message