From owner-freebsd-bugs  Mon Nov 18 11:01:44 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA04664
          for bugs-outgoing; Mon, 18 Nov 1996 11:01:44 -0800 (PST)
Received: from george.lbl.gov (george-2.lbl.gov [131.243.2.12])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA04642;
          Mon, 18 Nov 1996 11:01:37 -0800 (PST)
Received: (jin@localhost) by george.lbl.gov (8.6.10/8.6.5) id LAA10595; Mon, 18 Nov 1996 11:01:35 -0800
Date: Mon, 18 Nov 1996 11:01:35 -0800
From: "Jin Guojun[ITG]" <jin@george.lbl.gov>
Message-Id: <199611181901.LAA10595@george.lbl.gov>
To: hakers@freebsd.org
Subject: Re: MAXUSERS (was what is changed for ARP in 2.2-SNAP)
Cc: bugs@freebsd.org, jin@george.lbl.gov, questions@freebsd.org
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> In message <199611041928.LAA17022@george.lbl.gov> you write:
> >If some one would tell me what is core change for the ARP, so I can make
> >corresponding change in the ATM, it will be appriciated.
>...
> That was caused by maxusers which is limited to 15 in 2.2-SNAP ...

Actually, it is limited by NMBCLUSTERS = (512 + MAXUSERS * 16) in conf/param.c
2.2-ALPHA works better, which NMBCLUSTERS can be (512 + 18 * 16)

On same motherboard, the limit can be changed when the CPU clock changes.
For example, on Intel PT-2000 motherboard, if CPU clock is 100 MHz, the
limit of the maxusers for NMBCLUSTERS could vary from 0, 3 - 15
(some Motherboard does not work at all).
Changing CPU clock up to 120 MHz, the limit will stay at 15. (2.2-SNAPs)

I thought that might be caused by page boundary, but it doesn't look like
according to the behaves above.  I will keep to track down the problem
further. In the meantime, if any one has some idea what could cause this
kind of problems, please let me know.

Thanks,

-Jin