From owner-freebsd-hackers  Mon Apr  7 13:05:16 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id NAA06090
          for hackers-outgoing; Mon, 7 Apr 1997 13:05:16 -0700 (PDT)
Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [171.69.104.147])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA06085
          for <hackers@freebsd.org>; Mon, 7 Apr 1997 13:05:12 -0700 (PDT)
Received: from bmcgover-pc.cisco.com (localhost.cisco.com [127.0.0.1])
	by bmcgover-pc.cisco.com (8.8.5/8.8.5) with ESMTP id QAA16249
	for <hackers@freebsd.org>; Mon, 7 Apr 1997 16:04:40 -0400 (EDT)
Message-Id: <199704072004.QAA16249@bmcgover-pc.cisco.com>
To: hackers@freebsd.org
Subject: Limits on clist queues...
Date: Mon, 07 Apr 1997 16:04:39 -0400
From: Brian McGovern <bmcgover@cisco.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Does anyone know if the various line disciplines enforce upper limits
on the number of characters that can be buffered in the clist queues at 
any moment? Or is it a function of the device driver to limit itself? Or,
does it really not matter anymore, now that we have "tons" of memory to
play with?

	-Brian