From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Nychis Date: Tue, 11 Apr 2006 04:33:31 +0000 Subject: Re: [LARTC] created new q_disc, inserted module, tc tells me unknown Message-Id: <443B319B.7060407@cmu.edu> List-Id: References: <1737.128.2.140.234.1144719887.squirrel@128.2.140.234> In-Reply-To: <1737.128.2.140.234.1144719887.squirrel@128.2.140.234> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org Hey Tim, I will take a look at that routine, it just seems no matter what I do I cannot seem to find out why it determines it does not have xcp qdisc support. I will look deeper into it. I am not sure if it has been released to the public yet. I am using Yongguang Zhang and Tom Henderson's Linux implementation. I am also not sure it is the same packet formated as the ISI FreeBSD implementation. Tom pre-released it to me for my research on the topic, I think I will ask him if it is public yet, because if so I think I could find help a lot easier :) I will get back to you with what I find. Thanks! George Tim Shepard wrote: > To debug this you'll probably want to have a look at the > get_qdisc_kind() routine in tc/tc.c in the iproute sources and > understand how it uses dlopen() to find the routines to parse the > arguments to the various different qdisc implementations.. > > I hope this helps. > > > Is your xcp-implementing qdisc code available anywhere yet? Are you > using the same packet format as the folks at ISI are using in their > FreeBSD implementation? (They wrote a internet draft describing the > XCP packet format a year or two ago.) > > -Tim Shepard > shep@alum.mit.edu > _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc