From owner-freebsd-current@freebsd.org Mon Jan 8 05:17:24 2018 Return-Path: Delivered-To: freebsd-current@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 9CB58E7761C for ; Mon, 8 Jan 2018 05:17:24 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (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 5D2BC6962C for ; Mon, 8 Jan 2018 05:17:24 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x22c.google.com with SMTP id f143so7951474itb.0 for ; Sun, 07 Jan 2018 21:17:24 -0800 (PST) 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; bh=BHQV0Kp1UyhkPFMg7NqeFxCy2juyaUswJpQumvY1vBM=; b=oLhox9Dswo4ZCusUVvqO3Pzo+4+9R6HhMFI2ZmlQH6OhzcGaRjCU6EjbGQ3YYTeczL /8Fz3pBd6TJc3vIu20GbCEVuQIG639X45EInImWYQC0U0xmrlU2Eb60t6GUpmqXAlC1N VXEVHe7+dJYtx4s47ACeiLlnqeBzgtRHWjtUC66gUp1HBbXenAKkugXQ6zvE5SsY3NHV CDeyPEUxUxNqwLcuNQeAMoliu5qRSH9gXare4YyqGcmlIUmMNa0D8dYn+ujGoyxXUo4r Cpxy/4gx8T0PSAAJOx3sskFXjGz81sStLMxVwQ1i4WFDC1bn4X0+v9F9cq2eFoXjxU1r Fyog== 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; bh=BHQV0Kp1UyhkPFMg7NqeFxCy2juyaUswJpQumvY1vBM=; b=EZQHHt176MNgD47XTz0Sh1GVPLluqPUTt63QNxNwokg0QvxyoVUchbhfuIDsicwNux 1nQ9lH9b6Grcu6X3rDs6+iIuzL1VRwHNSDqJLJCZjmAijAvUM87S1Wa1T5P2ifo12hIW 6djJ56iYxNnI7nFxHet4K+z2KUn8DG1G/tHCDbEEOlU7gd15CPiAoAEP22MVFtwBoX/9 zK56vGyUyQYVzAVE6efrGtEXkvA4QdMwvZ9QFRl+6tBNJ6wzsz6Di4UomxIxHcYyKBM0 2ZW41Uf0POBzgrWWeMKq3hOPP/s7QJuF4ayF9BHbPuKQqmUcHlowQ2gAm7xk/q2hQrvl TEbg== X-Gm-Message-State: AKGB3mLgjI5BFrZQL6oSNx3z3Mqkt6zMH+EHh/kpIsdrhO6Wwh73TeUi PzGJGn9nVfw6RDJAny2+56dp1Be2N2Q549fGcpU= X-Google-Smtp-Source: ACJfBotD3jHhwNzk5qFBaFZ3VdxONu8ghPLKxlvCiYocun0TDUnygkhlyYpZK93mJodPT4XU45jkAYTIO1l3JeiAiPg= X-Received: by 10.36.112.65 with SMTP id f62mr10394441itc.51.1515388643519; Sun, 07 Jan 2018 21:17:23 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.164.203 with HTTP; Sun, 7 Jan 2018 21:17:22 -0800 (PST) In-Reply-To: <6ADAB19C-3EC6-476D-9B89-3B29EF9EC087@brawn.org> References: <1FD1FE97-D25C-4BAC-A3E0-F22509FB0C2B@dons.net.au> <6A4FF1B9-D98B-4E73-9E3E-E951749E0C21@dons.net.au> <20180104092349.2821f9f9@ernst.home> <18F01F2F-8907-4CF8-A80A-B6B5C16593B7@dons.net.au> <6ADAB19C-3EC6-476D-9B89-3B29EF9EC087@brawn.org> From: blubee blubeeme Date: Mon, 8 Jan 2018 13:17:22 +0800 Message-ID: Subject: Re: USB stack To: Jon Brawn Cc: Warner Losh , "O'Connor, Daniel" , gljennjohn@gmail.com, FreeBSD current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jan 2018 05:17:24 -0000 On Mon, Jan 8, 2018 at 8:03 AM, Jon Brawn wrote: > > > > On Jan 7, 2018, at 5:44 PM, Jon Brawn wrote: > > > > > >> On Jan 6, 2018, at 10:18 PM, blubee blubeeme > wrote: > >> > >> On Sun, Jan 7, 2018 at 12:11 PM, Warner Losh wrote: > >> > >>> > >>> > >>> On Sat, Jan 6, 2018 at 8:56 PM, blubee blubeeme > >>> wrote: > >>> > >>>> I ask does FreeBSD usb stack actually implements USB spec 2.0 or > greater > >>>> and the topic gets derailed...? > >>>> > >>> > >>> Yes, it does. > >>> > >>> > >>>> Are you guys saying that 7-8MB/s is USB speeds? > >>>> > >>> > >>> I've gotten up to 24MB/s for maybe a decade. That's not possible with > USB > >>> 1.x. More recently, I've maxed out the writes on a USB stick at about > >>> 75MB/s (the fastest it will do), which isn't possible with USB 2.0... > I've > >>> not tried USB3 with an SSD that can do more.... > >>> > >>> Warner > >>> > >>> > >>>> On Thu, Jan 4, 2018 at 6:44 PM, O'Connor, Daniel > >>>> wrote: > >>>> > >>>>> > >>>>> > >>>>>> On 4 Jan 2018, at 09:23, Gary Jennejohn > wrote: > >>>>>>> What is an "LG v30"? > >>>>>>> > >>>>>> It's a smartphone from LG and only supports USB2 speed. The > reported > >>>>>> transfer rate is no big surprise. > >>>>> > >>>>> OK thanks. > >>>>> > >>>>> -- > >>>>> Daniel O'Connor > >>>>> "The nice thing about standards is that there > >>>>> are so many of them to choose from." > >>>>> -- Andrew Tanenbaum > >>>>> GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C > >>>>> > >>>>> > >>>> _______________________________________________ > >>>> freebsd-current@freebsd.org mailing list > >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-current > >>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@ > freebsd.org > >>>> " > >>>> > >>> > >>> I just connected a Transcend StorageJet 1TB hdd not a mobile phone > >> ------------------------------------------------------------------- > >> Jan 7 11:56:56 blubee kernel: umass0 on uhub0 > >> Jan 7 11:56:56 blubee kernel: umass0: >> Transcend, class 0/0, rev 3.00/80.00, addr 4> on usbus0 > >> Jan 7 11:56:56 blubee kernel: umass0: SCSI over Bulk-Only; quirks = =3D > 0x0100 > >> Jan 7 11:56:56 blubee kernel: umass0:3:0: Attached to scbus3 > >> Jan 7 11:56:56 blubee kernel: da0 at umass-sim0 bus 0 scbus3 target 0 > lun 0 > >> Jan 7 11:56:56 blubee kernel: da0: Fixed Direc= t > >> Access SPC-4 SCSI device > >> Jan 7 11:56:56 blubee kernel: da0: Serial Number W9328YZN > >> Jan 7 11:56:56 blubee kernel: da0: 400.000MB/s transfers > >> Jan 7 11:56:56 blubee kernel: da0: 953869MB (1953525168 512 byte > sectors) > >> Jan 7 11:56:56 blubee kernel: da0: quirks=3D0x2 > >> Jan 7 12:06:08 blubee kernel: lock order reversal: > >> Jan 7 12:06:08 blubee kernel: 1st 0xfffffe07c26336c0 bufwait > (bufwait) @ > >> /usr/src/sys/vm/vm_pager.c:374 > >> Jan 7 12:06:08 blubee kernel: 2nd 0xfffff80148c425f0 zfs (zfs) @ > >> /usr/src/sys/dev/md/md.c:952 > >> Jan 7 12:06:08 blubee kernel: stack backtrace: > >> Jan 7 12:06:08 blubee kernel: #0 0xffffffff80acfa03 at > >> witness_debugger+0x73 > >> Jan 7 12:06:08 blubee kernel: #1 0xffffffff80acf882 at > >> witness_checkorder+0xe02 > >> Jan 7 12:06:08 blubee kernel: #2 0xffffffff80a41b8e at > >> lockmgr_lock_fast_path+0x1ae > >> Jan 7 12:06:08 blubee kernel: #3 0xffffffff81094309 at > VOP_LOCK1_APV+0xd9 > >> Jan 7 12:06:08 blubee kernel: #4 0xffffffff80b4ac36 at _vn_lock+0x66 > >> Jan 7 12:06:08 blubee kernel: #5 0xffffffff80611d32 at > mdstart_vnode+0x442 > >> Jan 7 12:06:08 blubee kernel: #6 0xffffffff806102ce at md_kthread+0x1= fe > >> Jan 7 12:06:08 blubee kernel: #7 0xffffffff80a2d654 at fork_exit+0x84 > >> Jan 7 12:06:08 blubee kernel: #8 0xffffffff80ef5e0e at > fork_trampoline+0xe > >> Jan 7 12:06:15 blubee kernel: lock order reversal: > >> Jan 7 12:06:15 blubee kernel: 1st 0xfffffe07c41d5dc0 bufwait > (bufwait) @ > >> /usr/src/sys/kern/vfs_bio.c:3562 > >> Jan 7 12:06:15 blubee kernel: 2nd 0xfffff8002bb31a00 dirhash > (dirhash) @ > >> /usr/src/sys/ufs/ufs/ufs_dirhash.c:281 > >> Jan 7 12:06:15 blubee kernel: stack backtrace: > >> Jan 7 12:06:15 blubee kernel: #0 0xffffffff80acfa03 at > >> witness_debugger+0x73 > >> Jan 7 12:06:15 blubee kernel: #1 0xffffffff80acf882 at > >> witness_checkorder+0xe02 > >> Jan 7 12:06:15 blubee kernel: #2 0xffffffff80a748a8 at _sx_xlock+0x68 > >> Jan 7 12:06:15 blubee kernel: #3 0xffffffff80d6a28d at > ufsdirhash_add+0x3d > >> Jan 7 12:06:15 blubee kernel: #4 0xffffffff80d6d119 at > ufs_direnter+0x459 > >> Jan 7 12:06:15 blubee kernel: #5 0xffffffff80d76313 at > ufs_makeinode+0x613 > >> Jan 7 12:06:15 blubee kernel: #6 0xffffffff80d71ff4 at ufs_create+0x3= 4 > >> Jan 7 12:06:15 blubee kernel: #7 0xffffffff810919e3 at > VOP_CREATE_APV+0xd3 > >> Jan 7 12:06:15 blubee kernel: #8 0xffffffff80b4a53d at > vn_open_cred+0x2ad > >> Jan 7 12:06:15 blubee kernel: #9 0xffffffff80b42e92 at > kern_openat+0x212 > >> Jan 7 12:06:15 blubee kernel: #10 0xffffffff80f16d2b at > amd64_syscall+0x79b > >> Jan 7 12:06:15 blubee kernel: #11 0xffffffff80ef5b7b at > Xfast_syscall+0xfb > >> > >> > >> Is the slow transfers user error? > > > > Wotcha! > > > > I don=E2=80=99t see any read or write performance figures anywhere? Als= o, is > this CURRENT? If so, aren=E2=80=99t all the debug / warning features that= are > turned on by default in CURRENT at the moment going to have an effect on > throughput? Especially if you=E2=80=99re writing through a filesystem whe= re > directory and file accesses will each require a lock to be taken, if only > for a short while? If you want to get closer to the true USB speed of the > device, stop mounting it and copying files to the filesystem, but instead > just dd data onto and off of the device directly, and measure how fast th= at > goes. Remember to backup your data from the card first=E2=80=A6 > > > > Jon. > > > > > > Also, is the SD card physically inside the phone, and you are using a USB > cord to connect the phone to the FreeBSD computer by any chance? > > Jon > > @Mark Millard I use sysutils/simple-mtpfs to mount the android device. when I mount the phone through USB this is the relevant section: /dev/fuse 356311 78912 277398 22% /mnt That's the most complicated mount process that I use, for the ssd it's just a simple mount /dev/device /mnt relevant output: /dev/da0 923913 121450 728550 14% /mnt Can you tell me what information you're looking for so that I can gather it all up and send it. @Jon Brawn I am running current because I handle admin a few other boxes that are on RELEASE so I have to run in current to make sure they don't have it. I do wonder about those locks as well but, they should only affect the multiple small files, not so much the larger files. The microsd card is physically inside the phone.