From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-74.mimecast.com (us-smtp-delivery-74.mimecast.com [63.128.21.74]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 9478F3B2A4 for ; Fri, 27 Mar 2020 07:05:23 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1585307123; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=0qb/czQw2Lf8oH7KLHfCaW0CUPFc0F6u/eVrUjGw3lA=; b=ByJfOhSmZU27LKh5BYeU6Z9oJL6JaHOlGjm5LuFThnk8y0X57YigMBfXlbi656i2WW5Gqu iOu/fnY3y6d2HIpN8yW1zVuss1ZLTlmE6NY2ONepj0xqZD/6PMeowBV9wa/TZNUcz2LDqV yrlGizLSvTyl4r/CF5rIzm1v4IQj2d4= Received: from mail-lf1-f69.google.com (mail-lf1-f69.google.com [209.85.167.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-292-RP_Z5ocDNtGZbkgt8Tqvrg-1; Fri, 27 Mar 2020 07:05:16 -0400 X-MC-Unique: RP_Z5ocDNtGZbkgt8Tqvrg-1 Received: by mail-lf1-f69.google.com with SMTP id p8so132838lfc.8 for ; Fri, 27 Mar 2020 04:05:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=IgFuRZ7uJweluL1q4ays06EEUFmOZDunvI3f96HntXE=; b=oJbvvHfIzg/SJBXoj0AURkxwJfauqsz13H7tI1HlA7VpJJQpi1OfSSEOAX5V/j8E8J NNBUQCKcq14/Z9dEM/eGT57H/F+cofIWmGFLJm+QoXPIstzTAekoEa4UvTCTnmHxMuc5 Jw6isuzGvt4GXFiuCcNdMuwbQtPf/Lx1pdiC/0UUzoqX/8Ef23LB1+yZeR/VjTW4ls2T lmn3ph9QONDfq7TodSMJtFQ1bUVV2wNcAvuoIdtGNf1ZG6y5DmZx5TCqS1lIrO1ygZtS kDAPn/Bxhat4zkMfRKN3X58tujFqt7iqi+KRUfPHY6ah7OHy7yQQPJFs7i5kgQs7upBt k7uQ== X-Gm-Message-State: ANhLgQ0oVT3EpGPPuoYZaOq/XnJJUgT3707T1X7NcE+TmCeCJ1k/ltEv QpX+kt2IsvDOxAnEtUrrQjKeeq7Y6RQhR6edNXRLbbIZ01TvpHNsohQa47L5TLeERoHZbiNM451 xdN2hB3MDjTRlpVYi0tUQboMZKpOmkdGZoH8= X-Received: by 2002:a2e:9284:: with SMTP id d4mr7739155ljh.226.1585307114406; Fri, 27 Mar 2020 04:05:14 -0700 (PDT) X-Google-Smtp-Source: APiQypL0ApPPGDxQWW9JZbSbhT1yKSn5+6XJSssoLXir+sDPCffek8kCTI5pqjcngDMc2f4I10hsOA== X-Received: by 2002:a2e:9284:: with SMTP id d4mr7739129ljh.226.1585307113957; Fri, 27 Mar 2020 04:05:13 -0700 (PDT) Received: from alrua-x1.borgediget.toke.dk ([2a0c:4d80:42:443::2]) by smtp.gmail.com with ESMTPSA id m3sm539004lfb.59.2020.03.27.04.05.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 27 Mar 2020 04:05:13 -0700 (PDT) Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id 4102E18158B; Fri, 27 Mar 2020 12:05:10 +0100 (CET) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= To: Tim Higgins , Make-Wifi-fast Cc: flent-users@flent.org In-Reply-To: <1697eb13-068d-f518-35d6-1d1495feab40@smallnetbuilder.com> References: <1697eb13-068d-f518-35d6-1d1495feab40@smallnetbuilder.com> X-Clacks-Overhead: GNU Terry Pratchett Date: Fri, 27 Mar 2020 12:05:10 +0100 Message-ID: <87r1xem521.fsf@toke.dk> MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Subject: Re: [Make-wifi-fast] Flent traffic direction convention X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Mar 2020 11:05:23 -0000 (Adding flent-users@flent.org - please also include this in Flent-specific questions) > I might be confusing myself, but need to ask the question. What does flen= t > define as upload and download? > > Netperf docs say: > The TCP_STREAM test is the default test in netperf. It is quite simple, > transferring some quantity of data from the system running netperf to the > system running netserver. > > So why, when I look at tcp_1up_noping.conf does the DATA_SETS have 'test'= : > 'TCP_STREAM' in the 'TCP_upload' dictionary? Flent considers itself the client, so 'upload' is TCP_STREAM. As more use cases have emerged, this has turned out to not always be the case, of course; WiFi test scenarios such as you are doing being the most prominent example. There's a --swap-up-down parameter which will switch all instances of TCP_STREAM to TCP_MAERTS and vice-versa, though. > Second question: Is there any documentation that can help me figure out > exactly what traffic is running in each test type? > I've tried looking at the .conf and .inc files, in flent/tests but can't > figure it out. Not really :/ There's https://flent.org/tests.html, but it hasn't really kept up with new tests being added. However, you can see it after the fact: The exact command lines for each data series is stored (along with a bunch of other data) in the SERIES_META object in the data file. Use the GUI to browse this, or print it with 'flent -f metadata datafile.flent.gz'. -Toke