From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vc0-x22a.google.com (mail-vc0-x22a.google.com [IPv6:2607:f8b0:400c:c03::22a]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 0AEEA21F2F1 for ; Sun, 1 Mar 2015 07:19:38 -0800 (PST) Received: by mail-vc0-f170.google.com with SMTP id hq12so9446420vcb.1 for ; Sun, 01 Mar 2015 07:19:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=RFcKbvyHoK79HGmDWnw+fTTRMWipfmN0r2F+iomhVEI=; b=DjdCyilVcE+MXllpGZ89pCN40f7xut7gL2hq2is1RbCfVRG6bH7g4IBop/FG0T7Yoh t1fv8K9dxNgQCsfdhWmIjTyo3lQejzRZiG6VKqFvcCrFlM5t0WP4geKkAAqQfGMjcXkm e/dcLgO9epWRs/WmGEnZ8ENGzJl2uAX982yGWpTsi4Fpc2LAWcYucyHbGX+igQkXe6pI s8PveW/ahYbcRiUDz6S1RWDPc/CkpKCIFauAspBgNr/buuq+DZqYz6emB9Z42buSu7nJ hfpFbOdLX3PXHa4jkzAlse8SQlPcjs2y8c66j7mVQv47shxvQJROAj07A1QIE+yrQJmD 7q+A== MIME-Version: 1.0 X-Received: by 10.52.3.74 with SMTP id a10mr21251701vda.95.1425223176600; Sun, 01 Mar 2015 07:19:36 -0800 (PST) Received: by 10.52.24.79 with HTTP; Sun, 1 Mar 2015 07:19:36 -0800 (PST) Received: by 10.52.24.79 with HTTP; Sun, 1 Mar 2015 07:19:36 -0800 (PST) In-Reply-To: References: Date: Sun, 1 Mar 2015 17:19:36 +0200 Message-ID: From: Jonathan Morton To: mandy ahuja Content-Type: multipart/alternative; boundary=20cf3033477f2ac13e05103ba113 Cc: codel@lists.bufferbloat.net Subject: Re: [Codel] queue-size(in terms of packets) for codel in ns-2.35 X-BeenThere: codel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: CoDel AQM discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Mar 2015 15:20:08 -0000 --20cf3033477f2ac13e05103ba113 Content-Type: text/plain; charset=UTF-8 If you know the size of the packets that will be using it, then it is simple to cover from one to the other. That's more likely in a simulator than the real world though. IIRC, TCP acks are usually 48 bytes, but this may vary if extension options and/or IPv6 are in use. Check this yourself on the traffic you're testing. In the forward data flow direction, expect most packets to be at the link segment size limit, 1500 bytes for Ethernet. But if you have heterogeneous or bidirectional traffic, this calculation breaks down. This may simply be one limitation of ns2. - Jonathan Morton --20cf3033477f2ac13e05103ba113 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

If you know the size of the packets that will be using it, t= hen it is simple to cover from one to the other. That's more likely in = a simulator than the real world though.

IIRC, TCP acks are usually 48 bytes, but this may vary if ex= tension options and/or IPv6 are in use. Check this yourself on the traffic = you're testing. In the forward data flow direction, expect most packets= to be at the link segment size limit, 1500 bytes for Ethernet.

But if you have heterogeneous or bidirectional traffic, this= calculation breaks down. This may simply be one limitation of ns2.

- Jonathan Morton

--20cf3033477f2ac13e05103ba113--