From owner-freebsd-hackers Sat Jul 3 10:31:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from etinc.com (et-gw.etinc.com [207.252.1.2]) by hub.freebsd.org (Postfix) with ESMTP id BAA9F1509D for ; Sat, 3 Jul 1999 10:28:40 -0700 (PDT) (envelope-from dennis@etinc.com) Received: from dbsys (dbsys.etinc.com [207.252.1.18]) by etinc.com (8.9.3/8.9.3) with SMTP id NAA17426; Sat, 3 Jul 1999 13:24:07 -0400 (EDT) Message-Id: <199907031724.NAA17426@etinc.com> X-Sender: dennis@etinc.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 03 Jul 1999 12:20:35 -0400 To: Stan Shkolnyy From: Dennis Subject: Re: mbufs question/problem Cc: hackers@FreeBSD.ORG In-Reply-To: References: <199906302150.RAA01512@etinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:10 PM 7/2/99 -0500, Stan Shkolnyy wrote: >On Wed, 30 Jun 1999, Dennis wrote: > >> >> I have a customer who has been experiencing "slow downs" with a freebsd >> router....they have substantially increased performance by reducing >> MINCLSIZE. I havent tracked the source, but im trying to hypothesize what >> it might be. On the surface I cant see any relationship since very few >> routines seem dependent on that value (m_devget() in particular, but I dont >> believe they are using any driver that use it). Is it possible that they >> are running out of small mbufs (they have NMBCLUSTERS set to a very high >> value)? >> >> Any ideas would be helpful. > >I have not noticed answers so far, so maybe their drivers copy mbufs very >often. AFAIK, "small" mbufs are indeed copied but "cluster" ones are not, so >when they forced the system to use more "cluster" mbufs, they got >substantial savings on copy operations. Well they are using Intel cards and our sync boards (of course our driver is binary so the change wouldnt effect our driver), and I dont see the fxp driver using small buffers. They are running bgp4...but I dont know what kind of buffers are used for routes. Dennis > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message