From owner-freebsd-arm@freebsd.org Thu Sep 7 00:13:24 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1600AE1F0A0 for ; Thu, 7 Sep 2017 00:13:24 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 64178680F1 for ; Thu, 7 Sep 2017 00:13:23 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-lf0-x22b.google.com with SMTP id 80so16292402lfy.4 for ; Wed, 06 Sep 2017 17:13:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=QxZhqScDn0Yq6CyAN35QI1X50pP3JqWgqdF2UyTwLRI=; b=hkZCMz+lf31scPUGCPp248KWs6Cr+h/XlWdZ20x4fiYOIwHvCRom1ttWMHbRttWmZT TXzt0vkmEfyyKVDWlMrDG5HhUOHozt24SVyjeLOLQmnIqDtmpPWiRHaID5ruhSJXYiI8 wa6ECt02m00XKvxTrwg64HByfhCB3/r0SDZ2PB8gsXeagc6C6uGTKeTYXN91Ca2rLPgA 2wualqjoKB8HuriM/BefHnxQ0+zp/VqtYkoBoZF9eKNmX6nkGjmz3KLT42MtoSNChGdv QpbhmX8WZYyM7Y2u+qJzXe0nFV4W7cz4P2uwGVKpeBUYB4P5uTn/V5XL2JwoLneMTwuq mEww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=QxZhqScDn0Yq6CyAN35QI1X50pP3JqWgqdF2UyTwLRI=; b=rBQ+xkHXgRWRJI+bbWCezN6xS9Y8pxkg6yiUqxEFFYkKEH9iPBCsiuaI5+qiYp81/i hu5jZY1RouhAl/K8XkIVRi4QEKaG5Mz5xtdzGNjLzEhKO9zzZf/Zj38nTJ2hs8eQvBKq Ez3J0KP1V6KWw+31e3uby1P78vykFl1DsGWgdlaKE79hp3Gnbgm1UE9e0ay9ZBgtq5mC xxY1M4WmztnMBYTdWONA62UJhebvoJMeyjcrvLai2GvISp8QatXzYfwbF+LJa+DES54J 00wPPYzJfM/uE49THsiTQ+M+pQNStTcJnYFLmyC0p/HoniP9T2Kswoph+1JutgLipxhY jh0Q== X-Gm-Message-State: AHPjjUgTrXgHdUVEZuqm5UhVA8dtV0ChcXoxTmJ0QRVFF25YXejJKe9e j2Xo277n1mXmq8diq1f6OllgSxs2dA== X-Google-Smtp-Source: AOwi7QCWk/nD0ycITxiAEjDvQF64QOP11OVCDi0UoNHWXrKKvAV0uYchuku1JsbgZmo8snFGvIUGKQCYj4hOwLZ/fsc= X-Received: by 10.25.202.77 with SMTP id h13mr307703lfj.54.1504743200238; Wed, 06 Sep 2017 17:13:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.81.18 with HTTP; Wed, 6 Sep 2017 17:13:19 -0700 (PDT) In-Reply-To: References: <40EA308E-489D-4A0B-B75A-2CA5A4EC474E@theory14.net> <685d0eed3532a34f239e7ff893f817db@bakulin.de> <20170905141711.6545490.14963.31294@gmail.com> <656A5193-7389-476C-AF58-EB013E9155F3@theory14.net> From: Russell Haley Date: Wed, 6 Sep 2017 17:13:19 -0700 Message-ID: Subject: Re: Beaglebone Black + FreeBSD + USB WiFi = WAP? To: Chris Gordon Cc: freebsd-arm Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Sep 2017 00:13:24 -0000 On Wed, Sep 6, 2017 at 3:30 PM, Chris Gordon wrote: > Russ, > >> Have you monitored your system on a serial console or direct console >> (i.e. via hdmi/keyboard)? Is the system still responding to other >> commands after you run the speed test? My thought is that the really >> really low bandwidth belies a kernel panic on the main terminal that >> you are not seeing. > > I have a serial console connected the entire time along with ssh sessions= (via wired NIC) into the BBB. There is no panic other other messages on t= he console. The devices remains responsive to user input/actions via ssh. = In a previous reply to my initial inquiry, Ilya Bakulin asked about output = from "top -Sa=E2=80=9D thinking the CPU was overwhelmed. The system stays = at >90% idle through the entire test (upload and download). I see 2-4% WCP= U for interrupts and 1-2% for USB. Good, thanks for clarifying. >> If you would like to do some further testing, you could perhaps help >> me answer these things: > > It won=E2=80=99t be until next week when I can look at any of these. I= =E2=80=99m one of the organizers at vBSDcon and will be at the Dev Summit a= nd conference through the weekend. If anyone is interested, I=E2=80=99m ha= ppy to bring my BBB there for debugging/testing on site. Argh! I was just in Maryland and we flew home from Dulles!!! I made the client push the date forward to last week so I could be home for Labour Day. Have fun! (sob, sob, sob). ;) >> - Can you find a command line way of measuring throughput and latency >> separately that can be run on a host and on the bbb? I'm sure there >> are lots of ways to do so. I will leave it up to you to decide and >> will adopt the same tests so we can compare results. > > I just have to find another device -- I have everything wired here other = than i-devices. I used nuttcp for testing the wired connection, so I would= plan to use that for the Wifi. nuttcp. Got it, I'll start playing with it. >> - Can you run the bbb as a standard device (not an access point) and >> test the performance of the wlan0 interface using the method of >> measurement pointed above? I will do the same at some point with my >> wi-fi dongle. > > Yes, that should be easy to do, but will be next week before I have a cha= nce. > >> Some tests I would like to do: >> - Get DTrace involved as a debugging tool. I have rudimentary DTrace >> skills but will need to consult my books on how to measure throughput >> and latency. There are some examples early in the DTrace book of >> logging system calls made by a process and I will review that again >> when time permits. >> - Run the system through the kernel debugger. I think this is going to >> be difficult though as pausing the kernel in the middle of TCP traffic >> might invalidate any results I get. I know how difficult it can be to >> debug threaded applications, I can't see a kernel being any easier. ;) > > I was thinking along the same lines and hampered only by lack of time and= specific knowledge of what to start poking (of course, this is a great wqy= to learn!). My random thought of the day is that the "down/receive" from eth0 to wlan0 is working somewhat correctly, but the "up/send" from wlan0 to eth0 is causing issues. This is coming from your throughput notes, and the fact I got a whole page downloaded, but received a panic when I was trying to request another page. My thought is to start looking at the send commands for wlan0 and USB. > Thanks for your help. I=E2=80=99ll get some info as soon as I can. Anyt= hing important I=E2=80=99ll add to the bug report. Thanks for having a fun problem to play with! Good luck with the conference and don't worry about time, I have 3 other things that I started this week alone. Anyone want to test a prototype Lua database? lolz. Russ