From owner-freebsd-hackers  Tue Sep  3 21:31:44 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id VAA20783
          for hackers-outgoing; Tue, 3 Sep 1996 21:31:44 -0700 (PDT)
Received: from misery.sdf.com (misery.sdf.com [204.244.210.193])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id VAA20777
          for <hackers@freebsd.org>; Tue, 3 Sep 1996 21:31:41 -0700 (PDT)
Received: from localhost (tom@localhost) by misery.sdf.com (8.7.5/8.7.3) with SMTP id VAA10813 for <hackers@freebsd.org>; Tue, 3 Sep 1996 21:48:23 -0700 (PDT)
Date: Tue, 3 Sep 1996 21:48:22 -0700 (PDT)
From: Tom Samplonius <tom@sdf.com>
To: hackers@freebsd.org
Subject: Impact of large listen() queue
Message-ID: <Pine.NEB.3.94.960903214335.10629A-100000@misery.sdf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


  What is the impact of using a large value (>100) for the backlog param
to listen()?  Does it impact performance?  I assume that it eats some kind
of kernel memory space, so how much?

  I know there is an old standard of a maximum of 5 for the backlog param.
But most modern systems can handle much large values.  Is there any
disadvantage to using the maximum value (I believe under FreeBSD, this is
255) all the time?

Tom