From: Andrea Vai <andrea.vai@unipv.it>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-usb@vger.kernel.org, stern@rowland.harvard.edu
Subject: Re: Slow I/O on USB media
Date: Thu, 06 Jun 2019 10:41:35 +0200 [thread overview]
Message-ID: <2387746fa7c61a4fe9a994cbece186731eac7fa9.camel@unipv.it> (raw)
In-Reply-To: <20190605173902.GE27700@kroah.com>
Il giorno mer, 05/06/2019 alle 19.39 +0200, Greg KH ha scritto:
> On Wed, Jun 05, 2019 at 06:23:58PM +0200, Andrea Vai wrote:
> [...]
> In ssh I manually mount the media,
> then
> > run
> >
> > touch begin
> > date
> > <cp command>
> > date
> > touch end
>
> That tests nothing other than the size of the memory in your system
> :(
>
> You have to flush the data out to the device fully in order to
> properly
> measure device throughput. Calling 'touch' does not do that.
>
> > If I use the DE (where the media is mounted automatically) I used
> to
> > "eject" the media after the copy finished, and took note of the
> time
> > used until the media was correctly "ejected" (and, so, unmounted).
>
> eject/unmount is good.
>
> > Anyway, I know that I can do all of this in a better way, and will
> let
> > you know.
>
> Yes, please do so, your steps above do not show much.
so, just to be sure now, here is my test script:
touch inizio
date
mount UUID="6a9d3c05-6758-49c0-a46e-6ce221478eb3" /mnt/pendrive
cp /NoBackup/buttare/ubuntu-14.04.5-desktop-i386.iso /mnt/pendrive
umount /mnt/pendrive
date
touch fine
can you please confirm (if) it's fine?
>
> And you need to get your auto-mount out of the way, as who knows
> what
> options your device is being mounted with (i.e. sync or no
> sync). You
> have to control that yourself in order to be sure.
yes, I disabled the auto-mount. Furthermore, is there any option I
need to specify to the mount command (i.e., as you say, sync or no
sync)?
thanks,
bye
Andrea
next prev parent reply other threads:[~2019-06-06 8:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 13:18 Slow I/O on USB media Andrea Vai
2019-05-30 13:25 ` Greg KH
2019-06-03 11:13 ` Andrea Vai
2019-06-04 5:43 ` Greg KH
2019-06-04 7:26 ` Andrea Vai
2019-06-05 7:36 ` Andrea Vai
2019-06-05 14:26 ` Alan Stern
2019-06-05 15:46 ` Andrea Vai
2019-06-05 16:11 ` Alan Stern
2019-06-05 14:55 ` Greg KH
[not found] ` <0c2adde7154b0a6c8b2ad7fc5258916731b78775.camel@unipv.it>
2019-06-05 16:23 ` Andrea Vai
2019-06-05 17:39 ` Greg KH
2019-06-06 8:41 ` Andrea Vai [this message]
2019-06-06 9:03 ` Andrea Vai
2019-06-06 14:00 ` Andrea Vai
2019-06-06 14:30 ` Alan Stern
2019-06-06 14:47 ` Greg KH
2019-06-07 7:59 ` Andrea Vai
2019-06-08 7:43 ` Andrea Vai
2019-06-08 9:29 ` Andrea Vai
2019-06-10 14:38 ` Greg KH
2019-06-11 6:48 ` Andrea Vai
2019-06-10 14:40 ` Alan Stern
2019-06-10 14:55 ` Andrea Vai
2019-06-10 16:20 ` Alan Stern
2019-06-17 15:52 ` Andrea Vai
2019-06-17 16:14 ` Alan Stern
2019-06-17 16:34 ` Andrea Vai
2019-06-17 17:28 ` Alan Stern
2019-07-01 17:52 ` Andrea Vai
2019-07-01 18:57 ` Alan Stern
2019-06-10 14:37 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2387746fa7c61a4fe9a994cbece186731eac7fa9.camel@unipv.it \
--to=andrea.vai@unipv.it \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).