From owner-freebsd-current Tue Apr 17 19:35: 1 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id D080537B43C for ; Tue, 17 Apr 2001 19:34:58 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.11.2) id f3I2Yuq17047; Tue, 17 Apr 2001 19:34:56 -0700 (PDT) (envelope-from dillon) Date: Tue, 17 Apr 2001 19:34:56 -0700 (PDT) From: Matt Dillon Message-Id: <200104180234.f3I2Yuq17047@earth.backplane.com> To: "E.B. Dreger" Cc: Alfred Perlstein , Greg Lehey , "Justin T. Gibbs" , Doug Barton , "current @ freebsd . org" Subject: Re: Kernel preemption, yes or no? (was: Filesystem gets a huge performance boost) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :IIRC, didn't the NT driver for some NIC (Intel?) switch to polling, :anyway, under heavy load? The reasoning being that you _know_ that you're :going to get something... why bother an IRQ hit? : :That said, IRQ distribution sounds like a good thing for the general case. Under a full load polling would work just as well as an interrupt. With NT for the network tests they hardwired each NIC to a particular CPU. I don't know if they did any polling or not. :> If you have one NIC then obviously you can't take multiple interrupts :> for that one NIC on different cpu's. No great loss, you generally don't :> want to do that anyway. : :Actually, I should think that one would _want_ to serialize traffic for a :given NIC. (I'm ignoring when one trunks NICs... speaking of which, :anyone have info on 802.3ad? ;-) Otherwise, one ends up with a race that :[potentially] screws up packet sequence. : :Eddy Yes. Also NICs usually have circular buffers for packets so, really, only one cpu can be processing a particular NIC's packets at any given moment. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message