From owner-freebsd-current  Wed Mar  4 19:57:11 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA17149
          for freebsd-current-outgoing; Wed, 4 Mar 1998 19:57:11 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17135
          for <current@FreeBSD.ORG>; Wed, 4 Mar 1998 19:57:04 -0800 (PST)
          (envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id TAA05622;
	Wed, 4 Mar 1998 19:38:30 -0800 (PST)
Message-Id: <199803050338.TAA05622@implode.root.com>
To: Mike Smith <mike@smith.net.au>
cc: dmaddox@scsn.net, Evan Champion <evanc@synapse.net>,
        Matthew Thyer <Matthew.Thyer@dsto.defence.gov.au>,
        shimon@simon-shapiro.org, current@FreeBSD.ORG
Subject: Re: silo overflows (Was Re: 3.0-RELEASE?) 
In-reply-to: Your message of "Wed, 04 Mar 1998 19:32:25 PST."
             <199803050332.TAA23822@dingo.cdrom.com> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Wed, 04 Mar 1998 19:38:30 -0800
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>> Add this to your system conf:
>> 
>> options		"MSIZE=256"
>
>Interesting; why change the mbuf size?  Is this a recommended change 
>for general operation, or is 128 bytes still preferred?

   You don't want to do that. Without other changes, our networking code
behaves poorly when MSIZE is not 128.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message