mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+linux@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Multi-file USB mass-storage copy from PC to Nokia N900 slow when  using CFQ
Date: Tue, 5 Jan 2010 10:07:22 -0600	[thread overview]
Message-ID: <58965d8a1001050807l31ddf8d1l55ebcfbadbfc206d@mail.gmail.com> (raw)

Hi,

Copying more than one file from my PC (kernel 2.6.32) to my Nokia N900
over USB mass storage mode is very slow when CFQ is the i/o scheduler.
The target uses vfat filesystem.

I am using iotop to monitor the I/O in general, plus I performed the
following test. file1 and file2 are each 700M and both housed on a
ramdrive for this test. They were deleted from the destination between
runs.

# one file at a time with sync in-between, fast speeds:
$ sync; time sh -c "cp file1 /mnt/usb; sync; cp file2 /mnt/usb; sync"

real    1m25.697s
user    0m0.005s
sys     0m2.509s

# copy two files in a row, then sync, speed is bad:
$ sync; time sh -c "cp file1 file2 /mnt/usb; sync"

real    6m51.439s
user    0m0.007s
sys     0m2.615s


Using all I/O schedulers, the speed of the first test was the same. So
it's only related to writing more than 1 file to the N900. The timing
results for the second test ended up as such:

cfq: 6m51.439s
noop: 3m0.733s
anticipatory: 1m44.348s
deadline: 1m36.804s


Also, in 2.6.31 the speed was four times slower, so the removal of old
pdflush code may have made a difference in this case. Copying 1
gigabyte takes about 1 minute at optimal speed, about 5 minutes using
CFQ in kernel 2.6.32, and took about 20 minutes using CFQ in kernel
2.6.31.

I thought you may be interested in case there's room to improve the
scheduler.  If you want any other info let me know!

Thanks
Paul

             reply	other threads:[~2010-01-05 16:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05 16:07 Paul Hartman [this message]
2010-01-05 22:25 ` Sitsofe Wheeler
2010-01-07 13:41 ` Corrado Zoccolo
2010-01-12  5:31   ` Paul Hartman

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=58965d8a1001050807l31ddf8d1l55ebcfbadbfc206d@mail.gmail.com \
    --to=paul.hartman+linux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®