From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) (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 448D221F2E5 for ; Sun, 1 Mar 2015 08:37:43 -0800 (PST) Received: by widex7 with SMTP id ex7so9371758wid.1 for ; Sun, 01 Mar 2015 08:37:42 -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=bIiuDQaCqkFbaU06WBXj1NLm3lwgkcnFzWFtgdnHeuk=; b=0ncV/2NvIivAraa9Xklv7HZqvoCEH6gr3JcdPbDchxKKy4cVt4b/RDg6L4GvnwnM4L 91tmlpXC/jSCyFB+2ieFmI4MFoF/mlWHVUfWO985DYiJQk6gWKEJ4x7XQDrYAjE/Imn5 ESHN7nSJiexkiZ7GM+sLs5TNd/H5OzT4ej3PvKh0ioBjN5PLQwdEOuuWWezyaqU/nvKV rs9LF27ZcPsHoymV/FkKtGyfQFNSYnXiPADxG2Rrj+hRBGkXTSnzQnCa9KpZK00o9gUw 2HWjBO8QaUvMZRONHAjo3LUl6sfTY28QBTbY6q1UNGEvk91tW6Gf6WltwR081xL1f3On a3MA== MIME-Version: 1.0 X-Received: by 10.194.94.1 with SMTP id cy1mr48563778wjb.127.1425227861934; Sun, 01 Mar 2015 08:37:41 -0800 (PST) Received: by 10.180.207.9 with HTTP; Sun, 1 Mar 2015 08:37:41 -0800 (PST) In-Reply-To: References: Date: Sun, 1 Mar 2015 08:37:41 -0800 Message-ID: From: mandy ahuja To: Jonathan Morton Content-Type: multipart/alternative; boundary=047d7bf0c39a6f4a7105103cb8ab 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 16:38:12 -0000 --047d7bf0c39a6f4a7105103cb8ab Content-Type: text/plain; charset=UTF-8 By knowing the packet size, next what?? On Sun, Mar 1, 2015 at 7:19 AM, Jonathan Morton wrote: > 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 > --047d7bf0c39a6f4a7105103cb8ab Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
By knowing the packet size, next what??

On Sun, Mar 1, 2015 at 7:19 AM= , Jonathan Morton <chromatix99@gmail.com> wrote:

If you know the size of the packe= ts 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 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


--047d7bf0c39a6f4a7105103cb8ab--