Received: (from majordomo@localhost)
	by oss.sgi.com (8.11.3/8.11.3) id f3K3vVb06657
	for netdev-outgoing; Thu, 19 Apr 2001 20:57:31 -0700
Received: from cs.bu.edu (root@CS.BU.EDU [128.197.10.2])
	by oss.sgi.com (8.11.3/8.11.3) with ESMTP id f3K3vUM06654
	for <netdev@oss.sgi.com>; Thu, 19 Apr 2001 20:57:30 -0700
Received: from csa.bu.edu (dhiman@csa [128.197.12.3])
	by cs.bu.edu (8.10.1/8.10.1) with ESMTP id f3K3vGt00550;
	Thu, 19 Apr 2001 23:57:16 -0400 (EDT)
Received: (from dhiman@localhost)
	by csa.bu.edu (8.10.1/8.10.1) id f3K3vCi22153;
	Thu, 19 Apr 2001 23:57:12 -0400 (EDT)
Date: Thu, 19 Apr 2001 23:57:12 -0400
From: Dhiman Barman <dhiman@cs.bu.edu>
To: diffserv-general@lists.sourceforge.net
Cc: linux-diffserv@lrc.di.epfl.ch, linux-net@vger.rutgers.edu,
   netdev@oss.sgi.com
Subject: scheduler 
Message-ID: <20010419235712.A21784@cs.bu.edu>
Reply-To: dhiman@cs.bu.edu
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: owner-netdev@oss.sgi.com
Precedence: bulk

Hi,
  This is especially for those who wrote network schedulers on Linux. I
have added another packet scheduler, but whenever I configure the scheduler
using 'tc', the screen dumps and the machines hangs. I cannot figure
why that fraction of code should affect the os. Any help ? Is there
any other way to test any packet scheduler other than using 'tc'. 

Thanks,
db
-- 
Weinberg's Principle:
	An expert is a person who avoids the small errors while
	sweeping on to the grand fallacy.