[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

BOUNCE rtl@rtlinux.org: Approval required: (fwd)



>From owner-rtl Sat Aug  4 14:02:08 2001
Received: from donor.he.cox.rr.com (24-163-114-44.he.cox.rr.com [24.163.114.44])
	by hq.fsmlabs.com (8.11.2/8.11.2) with ESMTP id f74K28s32288
	for <rtl@fsmlabs.com>; Sat, 4 Aug 2001 14:02:08 -0600
Received: from emerging.org (localhost.localdomain [127.0.0.1])
	by donor.he.cox.rr.com (Postfix) with ESMTP id 3DDE02F9
	for <rtl@fsmlabs.com>; Sat,  4 Aug 2001 20:01:49 -0400 (EDT)
Sender: msherer@donor.he.cox.rr.com
Message-ID: <3B6C8CED.1FAC16D9@emerging.org>
Date: Sat, 04 Aug 2001 20:01:49 -0400
From: Matt Sherer <chaos@emerging.org>
Reply-To: chaos@emerging.org
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: rtl@fsmlabs.com
Subject: Re: [rtl] regd mbuff
References: <949ACC17102DD045AAB154CEB75A7EC402B10D77@xch-nw-21.nw.nos.boeing.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

"Basham, Richard R" wrote:
> 
> Here is an exchange I had with Tomasz a while back regarding mbuff and buffer sizes.  I am not sure if this is the definitive answer but it may help a few people out.
> 
> It is a little long winded but it covers a lot of investigation effort.

...

> 
> I checked SHMAX and yes indeed it is set to 32 MB.  It says in the file not to change that value >because so many others depend on that value.  Therefore I will not change that value.

AFAIK, modifying SHMMAX via sysctl is perfectly safe, although I don't
know if it affects the problem you're seeing.  Don't bother with
changing the source, just echo a new val (in bytes) to
/proc/sys/kernel/shmmax.  I've found it to be safe at 700 megs, which
was used to help Oracle chew through large data sets.  I believe there
is a maximum on the size at around a gig, but I'm not sure where that is
documented. (If it is documented.)

--Matt Sherer

----- End of forwarded message from owner-rtl@fsmlabs.com -----