From owner-freebsd-net Sat Oct 27 1:43:55 2001 Delivered-To: freebsd-net@freebsd.org Received: from server.soekris.com (soekris.com [216.15.61.44]) by hub.freebsd.org (Postfix) with ESMTP id 79DE037B403 for ; Sat, 27 Oct 2001 01:43:53 -0700 (PDT) Received: from soekris.com (1.4.soekris.com [192.168.1.4] (may be forged)) by server.soekris.com (8.9.2/8.9.2) with ESMTP id BAA27034; Sat, 27 Oct 2001 01:43:58 -0700 (PDT) (envelope-from soren@soekris.com) Message-ID: <3BDA73C0.73DBCAE9@soekris.com> Date: Sat, 27 Oct 2001 01:43:44 -0700 From: Soren Kristensen Organization: Soekris Engineering X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Luigi Rizzo Cc: net@FreeBSD.ORG Subject: Re: NEW CODE: polling support for device drivers. References: <20011027005905.A72758@iguana.aciri.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Luigi and all, That looks very interesting to me.... I would like to follow up with a question, just because of my interest in getting maximum packet forwarding performance out of FreeBSD.... As I see it, the advantage of the polling code is to avoid interrupts and context switches. Is it possible to implement all the basic packet forwarding to run to completion at interrupt, ie, when a packet comes in, the interrupt code would run until the packet has been sent out on another interface, and then loop back to see if there's more incomming packets, in a polling fashion. That would give the advantage of the polling, but without the latency. I'm mostly a hardware guy, so bear over with me if it's not possible at all.... Regards, Soren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message