Subject: Re: port-i386/34186 (msgbuf allocation)
To: None <port-i386-maintainer@netbsd.org, gnats-admin@netbsd.org,>
From: Pavel Cahyna <pavel@NetBSD.org>
List: netbsd-bugs
Date: 12/05/2006 09:05:03
The following reply was made to PR port-i386/34186; it has been noted by GNATS.

From: Pavel Cahyna <pavel@NetBSD.org>
To: Blair Sadewitz <blair.sadewitz@gmail.com>
Cc: gnats-bugs@netbsd.org
Subject: Re: port-i386/34186 (msgbuf allocation)
Date: Tue, 5 Dec 2006 09:04:31 +0000

 On Sun, Dec 03, 2006 at 11:39:16AM -0500, Blair Sadewitz wrote:
 > The msgbuf allocation fix seems to work as intended when
 > MSGBUF_MAX_SEG is defined to a larger value.  If it is approved by
 > christos et. al., I'd appreciate it being added to i386 and amd64.
 > 
 > Should MSGBUFSIZE now be derived from MSGBUF_MAX_SEG to avoid
 > redundancy?  Specifying both seems overly complex.
 
 No, because the size of message buffer has no simple relationship to the
 number of segments used.
 
 There is VM_PHYSSEG_MAX constant which is the maximum number of physical memory
 segments. It should be used instead of MSGBUF_MAX_SEG imo.