Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755671Ab1CBQw0 (ORCPT ); Wed, 2 Mar 2011 11:52:26 -0500 Received: from mail-fx0-f46.google.com ([209.85.161.46]:60452 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752103Ab1CBQwY (ORCPT ); Wed, 2 Mar 2011 11:52:24 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=pYDrIpuceIu2LUSBa3yizBC7+L+DRKi4g4inKcEnlkxvZJXq65If79Cg7GRdfbG1v8 99lJTukSqS6SJWSCp7q+uMSKfEicnbBMWVJ1kvdV+wz2GZgXYpXyV3/8WIw+zvUE+eQ2 Q6hcpzCkuqUIRBrbL/fwkBFzuFGzJmQ9mMOkU= Subject: Re: txqueuelen has wrong units; should be time From: Eric Dumazet To: Mikael Abrahamsson Cc: Stephen Hemminger , John Heffner , Bill Sommerfeld , Hagen Paul Pfeifer , Albert Cahalan , Jussi Kivilinna , linux-kernel , netdev@vger.kernel.org In-Reply-To: References: <1298793252.8726.45.camel@edumazet-laptop> <20110227125540.40754c5y78j9u2m8@hayate.sektori.org> <20110301222531.24832a93@nehalam> <20110301230754.5ef4ab35@nehalam> Content-Type: text/plain; charset="UTF-8" Date: Wed, 02 Mar 2011 17:50:44 +0100 Message-ID: <1299084644.2920.24.camel@edumazet-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1273 Lines: 38 Le mercredi 02 mars 2011 à 17:41 +0100, Mikael Abrahamsson a écrit : > On Tue, 1 Mar 2011, Stephen Hemminger wrote: > > > Also WRED is not default on faster links because it can't be done fast > > enough. > > Before this propagates as some kind of truth. Cisco modern core routers > have no problems doing WRED at wirespeed, the above statement is not true. > looking at cisco docs you provided ( ) , it seems the WRED time limits (instead of bytes/packets limits) are internaly converted to bytes/packets limits quote : When the queue limit threshold is specified in milliseconds, the number of milliseconds is internally converted to bytes using the bandwidth available for the class. So it seems its only a facility provided, and queues are still managed with bytes/packets limits... WRED is able to prob drop a packet when this packet is enqueued. At time of enqueue, we dont know yet the time of dequeue, unless bandwidth is known. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/