From owner-freebsd-hardware Tue Oct 31 14:41:15 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from portnoy.lbl.gov (portnoy.lbl.gov [131.243.2.11]) by hub.freebsd.org (Postfix) with ESMTP id 7251837B4C5 for ; Tue, 31 Oct 2000 14:41:14 -0800 (PST) Received: (from jin@localhost) by portnoy.lbl.gov (8.11.1/8.11.1) id e9VMfDr07348 for freebsd-hardware@FreeBSD.ORG; Tue, 31 Oct 2000 14:41:13 -0800 (PST) Date: Tue, 31 Oct 2000 14:41:13 -0800 (PST) From: Jin Guojun (DSD staff) Message-Id: <200010312241.e9VMfDr07348@portnoy.lbl.gov> To: freebsd-hardware@FreeBSD.ORG Subject: What is the main task chewing CPU in GigE driver Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is following up a previous SysKonnect/NetGear/Intel GigE discussion on CPU utilization. I heard people talking that using Jumbo Frame on these GigE adapters will use less CPU time. Since I have not gotten a chance to paly the Jumbo Frame on these NICs, and it seems all these cards have the similar CPU utilization issue, I would like to know which part of the drive process that chews more CPU when using the smaller MTU than using the larger MTU (assume without zero memory copy)? -Jin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message