Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 07 Jan 2018 21:40:24 -0800
From:      "Chris H" <bsd-lists@BSDforge.com>
To:        "blubee blubeeme" <gurenchan@gmail.com>
Cc:        "Warner Losh" <imp@bsdimp.com>, "OConnor, Daniel" <darius@dons.net.au>, <gljennjohn@gmail.com>, "FreeBSD current" <freebsd-current@freebsd.org>, "Jon Brawn" <jon@brawn.org>
Subject:   Re: USB stack
Message-ID:  <91e0e215f2568bc8f9d00988b7eaeae7@udns.ultimatedns.net>
In-Reply-To: <CALM2mEnsbS2WijTPzihEfP2K_7H5r1hRXGuCCsuyzbw7MwA03w@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 8 Jan 2018 13:17:22 +0800 "blubee blubeeme" <gurenchan@gmail=2Ecom> s=
aid

> On Mon, Jan 8, 2018 at 8:03 AM, Jon Brawn <jon@brawn=2Eorg> wrote:
>=20
> >
> >
> > > On Jan 7, 2018, at 5:44 PM, Jon Brawn <jon@brawn=2Eorg> wrote:
> > >
> > >
> > >> On Jan 6, 2018, at 10:18 PM, blubee blubeeme <gurenchan@gmail=2Ecom>
> > wrote:
> > >>
> > >> On Sun, Jan 7, 2018 at 12:11 PM, Warner Losh <imp@bsdimp=2Ecom> wrote:
> > >>
> > >>>
> > >>>
> > >>> On Sat, Jan 6, 2018 at 8:56 PM, blubee blubeeme <gurenchan@gmail=2Eco=
m>
> > >>> wrote:
> > >>>
> > >>>> I ask does FreeBSD usb stack actually implements USB spec 2=2E0 or
> > greater
> > >>>> and the topic gets derailed=2E=2E=2E?
> > >>>>
> > >>>
> > >>> Yes, it does=2E
> > >>>
> > >>>
> > >>>> Are you guys saying that 7-8MB/s is USB speeds?
> > >>>>
> > >>>
> > >>> I've gotten up to 24MB/s for maybe a decade=2E That's not possible wi=
th
> > USB
> > >>> 1=2Ex=2E More recently, I've maxed out the writes on a USB stick at abo=
ut
> > >>> 75MB/s (the fastest it will do), which isn't possible with USB 2=2E0=2E=
=2E=2E
> > I've
> > >>> not tried USB3 with an SSD that can do more=2E=2E=2E=2E
> > >>>
> > >>> Warner
> > >>>
> > >>>
> > >>>> On Thu, Jan 4, 2018 at 6:44 PM, O'Connor, Daniel <darius@dons=2Enet=2E=
au>
> > >>>> wrote:
> > >>>>
> > >>>>>
> > >>>>>
> > >>>>>> On 4 Jan 2018, at 09:23, Gary Jennejohn <gljennjohn@gmail=2Ecom>
> > wrote:
> > >>>>>>> What is an "LG v30"?
> > >>>>>>>
> > >>>>>> It's a smartphone from LG and only supports USB2 speed=2E  The
> > reported
> > >>>>>> transfer rate is no big surprise=2E
> > >>>>>
> > >>>>> OK thanks=2E
> > >>>>>
> > >>>>> --
> > >>>>> Daniel O'Connor
> > >>>>> "The nice thing about standards is that there
> > >>>>> are so many of them to choose from=2E"
> > >>>>> -- Andrew Tanenbaum
> > >>>>> GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE=
8C
> > >>>>>
> > >>>>>
> > >>>> _______________________________________________
> > >>>> freebsd-current@freebsd=2Eorg mailing list
> > >>>> https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-current
> > >>>> To unsubscribe, send any mail to "freebsd-current-unsubscribe@
> > freebsd=2Eorg
> > >>>> "
> > >>>>
> > >>>
> > >>> 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: <StoreJet Transcend StoreJet
> > >> Transcend, class 0/0, rev 3=2E00/80=2E00, 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: <StoreJet Transcend 0> Fixed Dir=
ect
> > >> 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=2E000MB/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<NO_6_BYTE>
> > >> 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=2Ec:374
> > >> Jan  7 12:06:08 blubee kernel:  2nd 0xfffff80148c425f0 zfs (zfs) @
> > >> /usr/src/sys/dev/md/md=2Ec: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+0x6=
6
> > >> 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+0=
x1fe
> > >> Jan  7 12:06:08 blubee kernel: #7 0xffffffff80a2d654 at fork_exit+0x=
84
> > >> 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=2Ec:3562
> > >> Jan  7 12:06:15 blubee kernel:  2nd 0xfffff8002bb31a00 dirhash
> > (dirhash) @
> > >> /usr/src/sys/ufs/ufs/ufs_dirhash=2Ec: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+0x=
68
> > >> 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+0=
x34
> > >> 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? A=
lso, is
> > this CURRENT? If so, aren=E2=80=99t all the debug / warning features th=
at are
> > turned on by default in CURRENT at the moment going to have an effect o=
n
> > throughput? Especially if you=E2=80=99re writing through a filesystem w=
here
> > directory and file accesses will each require a lock to be taken, if on=
ly
> > for a short while? If you want to get closer to the true USB speed of t=
he
> > device, stop mounting it and copying files to the filesystem, but inste=
ad
> > just dd data onto and off of the device directly, and measure how fast =
that
> > goes=2E Remember to backup your data from the card first=E2=80=A6
> > >
> > > Jon=2E
> > >
> > >
> >
> > Also, is the SD card physically inside the phone, and you are using a U=
SB
> > 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=2E
> when I mount the phone through USB this is the relevant section:
> /dev/fuse                                   356311 78912 277398    22%
> /mnt
>=20
> 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
>=20
> Can you tell me what information you're looking for so that I can gather =
it
> all up and send it=2E
>=20
> @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=2E
It's not CURRENT that's the problem, but GENERIC (WITNESS et al; that cause=
s
contention) -- see; performance loss=2E :-)

> I do wonder about those locks as well but, they should only affect the
> multiple small files,
> not so much the larger files=2E
>=20
> The microsd card is physically inside the phone=2E
--Chris





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?91e0e215f2568bc8f9d00988b7eaeae7>