From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,T_DKIMWL_WL_HIGH, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C2FB9C64EB1 for ; Fri, 7 Dec 2018 18:35:20 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 8FB4820672 for ; Fri, 7 Dec 2018 18:35:20 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="RvGkF+w/" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 8FB4820672 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=epigenesys.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-amlogic-bounces+linux-amlogic=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=2RbcUD2CodHDhQuO+UHT7JommtH9HsLVgPoIuu/h3r4=; b=RvGkF+w/pyDjtC GKIZv3G9S5v56ZvXClyVHAlOs4fjWQh1cRCw7LPNH4Bb+xWEDReTIxf0llxEhlUFHPNk6JKa87HIv ZLaaNvtzCHdHgXs7hSRs2sat3PvKVEA/jgZscRqwy0bVweXop6gGQIDNT3GWd88Yuc3CmS9SxTCKc qG0/wm9jke8RZvu8GQFPhWkhQuuDH3D0aYw4Bi6eQEQYz4kQknjnMOiAXWOTq8v5+JNMIosgMULHU UAHthbULgkNDx6fKnPO0E8UMiBSpBaBcq0rKON954/3Z4lYqZ9hxX2sVGsvJLxSiKC0umd0UZBZ+N 9Q1Yhht9DvVo2Bi9WMlA==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.90_1 #2 (Red Hat Linux)) id 1gVKy2-0000W3-NW; Fri, 07 Dec 2018 18:35:14 +0000 Received: from mail-wm1-f65.google.com ([209.85.128.65]) by bombadil.infradead.org with esmtps (Exim 4.90_1 #2 (Red Hat Linux)) id 1gVKx1-0006yk-0v; Fri, 07 Dec 2018 18:34:16 +0000 Received: by mail-wm1-f65.google.com with SMTP id a18so5490863wmj.1; Fri, 07 Dec 2018 10:34:00 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=7OErVHsTz+9MWPsO58Jikl5ucj/hyhsAvpkjo2HRL7E=; b=rZzF7s+CfUGc5lFVZ8BxX2qgGjdl93F8N2lYs8DNV7YJKR18ngd2V9ylm0m0c/uKsy 9cG0n6bMiuINyh+QxwrU4acv6joXhoZ1LUHfiNuR8GjMkIHQzqPchHseQMsg3xx81MQF TlHnKZxOmHK0JPF3LSCgxI+zd8irmE+trLX96RalfwyYUZECzImgddUvmzXUwTytos1Z B1hssGwxi/5ne9Ccuv+nM2Vvcfo/rMXow9WheLBnGNBkBdzYMKOfB9h1VN4/XRkovF0g wisivmsMHiNEYVKVCFpMFuLjV7C3MRSCK53l5MeKEzBjmwifcGatjewROfVIZZMPlyrX pKDg== X-Gm-Message-State: AA+aEWbasQekTSq06bYe0mLUF40Dm3Np3ipgYJuwu8Kz1yTOTjsCNiza IFAAh64PBmHzfwDyXeKwVos= X-Google-Smtp-Source: AFSGD/X4G2+XJl+JhN8RDVP2LMggg81K4y0vL7qKDJ6QOumyqTioRUEkUYA/xEt8mJPJu4Pkn7ap9w== X-Received: by 2002:a1c:8104:: with SMTP id c4mr2867021wmd.133.1544207638938; Fri, 07 Dec 2018 10:33:58 -0800 (PST) Received: from ingrassia.epigenesys.com (host194-85-static.3-79-b.business.telecomitalia.it. [79.3.85.194]) by smtp.gmail.com with ESMTPSA id v132sm4772865wme.20.2018.12.07.10.33.57 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 07 Dec 2018 10:33:58 -0800 (PST) Date: Fri, 7 Dec 2018 19:33:55 +0100 From: Emiliano Ingrassia To: Carlo Caione , Martin Blumenstingl Subject: Re: [PATCH 0/2] meson: Fix IRQ trigger type Message-ID: <20181207183355.GA17435@ingrassia.epigenesys.com> References: <20181204160447.27869-1-ccaione@baylibre.com> <20181206124347.GA10676@ingrassia.epigenesys.com> <85973a9cd43c677ffa5c80853e86d79f36a9eb3a.camel@baylibre.com> <20181206155228.GA15225@ingrassia.epigenesys.com> <20181206185158.GA19901@ingrassia.epigenesys.com> <44c9eedf4dc2616645c2a49b080f42a493fe03fd.camel@baylibre.com> <463139583299c0099c812ad12017fe6d32662db4.camel@baylibre.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <463139583299c0099c812ad12017fe6d32662db4.camel@baylibre.com> User-Agent: Mutt/1.11.1 (2018-12-01) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20181207_103411_689969_A5F24FA8 X-CRM114-Status: GOOD ( 16.51 ) X-BeenThere: linux-amlogic@lists.infradead.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: mark.rutland@arm.com, devicetree@vger.kernel.org, khilman@baylibre.com, robh+dt@kernel.org, linux-amlogic@lists.infradead.org, linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-amlogic" Errors-To: linux-amlogic-bounces+linux-amlogic=archiver.kernel.org@lists.infradead.org On Fri, Dec 07, 2018 at 11:03:20AM +0000, Carlo Caione wrote: > On Fri, 2018-12-07 at 11:49 +0100, Jerome Brunet wrote: > > On Thu, 2018-12-06 at 19:51 +0100, Emiliano Ingrassia wrote: > > > Hi Carlo, > > > > > > I keep running tests with packet generator, > > > using nload to show bandwidth usage. > > > > > > Here is my test results with packet generators > > > both running on laptop and board with rate 1 Gbps. > > > > Testing in UDP is unlikely to give us clear picture of anything for > > this sort > > of fixes. > > > > All your test seems in show it the fact the Amlogic SoC usually > > prioritize the > > TX traffic over RX, which is something we've known about for a while. > > > > It would be helpful if you could provide TCP figures with a traffic > > generator > > we can all share an inspect, such as iperf3 > > For reference you can use something like: > > iperf3 -c ${IP} -i ${IPERF_LOGPERIOD} -w 400k -p ${PORT} -t ${DURATION} > Thanks Carlo. Just to be consistent, what value did you use for DURATION? > Cheers, > > -- > Carlo Caione > Regards, Emiliano _______________________________________________ linux-amlogic mailing list linux-amlogic@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-amlogic