From owner-freebsd-current@FreeBSD.ORG Thu May 29 03:53:25 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5DC36229 for ; Thu, 29 May 2014 03:53:25 +0000 (UTC) Received: from COL004-OMC3S7.hotmail.com (col004-omc3s7.hotmail.com [65.55.34.145]) by mx1.freebsd.org (Postfix) with ESMTP id 3DF0F25AA for ; Thu, 29 May 2014 03:53:24 +0000 (UTC) Received: from COL131-DS25 ([65.55.34.135]) by COL004-OMC3S7.hotmail.com with Microsoft SMTPSVC(7.5.7601.22678); Wed, 28 May 2014 20:53:17 -0700 X-TMN: [sPmUda+Xm0DznLeAR74e26hvH7WIM9Z0] X-Originating-Email: [fredhps10@hotmail.com] Message-ID: From: Fred Pedrisa To: "'Jan Bramkamp'" , References: <00c301cf7aee$b00caea0$10260be0$@rlwinm.de> In-Reply-To: <00c301cf7aee$b00caea0$10260be0$@rlwinm.de> Subject: RES: KQueue vs Select (NetMap) Date: Thu, 29 May 2014 00:53:41 -0300 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHirpLONkJpDgmFWk/rBALGUBsbjAGIqyNfmyRAhzA= Content-Language: pt-br X-OriginalArrivalTime: 29 May 2014 03:53:17.0886 (UTC) FILETIME=[8679A5E0:01CF7AF1] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 May 2014 03:53:25 -0000 Hello, Yes, but kqueue support was added in recent commits as it says in the netmap changelog, is there any advantage ? -----Mensagem original----- De: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freebsd.org] Em nome de Jan Bramkamp Enviada em: quinta-feira, 29 de maio de 2014 00:30 Para: freebsd-current@freebsd.org Assunto: Re: KQueue vs Select (NetMap) On 29.05.2014 03:04, Fred Pedrisa wrote: > Hey Guys, > > > > How does kQueue performs over select with netmap ? You are asking for a comparison between apples and oranges. Netmap is an API for high performance access to the low-level features of modern NICs. It works on batches of frames in hardware queues. The kqueue() and kevent() system calls are an event notification API. It is mostly used by application dealing with a large amount of non-blocking sockets (or other file descriptors). It reduces overhead inherent in select() and poll() by preserving state between calls. It also supports multiple types of events (read ready, write ready, timer expired, async i/o, etc.). Afaik the netmap pseudo-device supports only select() and poll(). This is no performance problem because every thread will only deal with a small number of file descriptors to netmap devices. Netmap is designed to bypass the FreeBSD IP stack (for most frames). Kqueue is designed to scale to many sockets per process within the FreeBSD IP stack. _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"