linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Shaohua Li <shaohua.li@intel.com>
Cc: Wu Fengguang <wfg@linux.intel.com>,
	Herbert Poetzl <herbert@13thfloor.at>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>, Jens Axboe <axboe@kernel.dk>,
	Tejun Heo <tj@kernel.org>
Subject: Re: Bad SSD performance with recent kernels
Date: Mon, 30 Jan 2012 06:31:59 +0100	[thread overview]
Message-ID: <1327901519.2891.4.camel@edumazet-laptop> (raw)
In-Reply-To: <CANejiEW86b7btiOcVFF3qVhqU1t6FRosvgfiydWwU5zgeDFOqw@mail.gmail.com>

Le lundi 30 janvier 2012 à 11:17 +0800, Shaohua Li a écrit :

> 1M block size is slow, I guess it's CPU related.
> 
> And as for the big regression with newer kernel than 2.6.38, please
> check if idle=poll
> helps. CPU idle dramatically impacts disk performance and even latest
> cpuidle governor
> doesn't help for some CPUs.
> 

No change with idle=poll

# echo 3 >/proc/sys/vm/drop_caches ;perf record dd if=/dev/sda
of=/dev/null bs=2M count=2048
2048+0 enregistrements lus
2048+0 enregistrements écrits
4294967296 octets (4,3 GB) copiés, 27,6942 s, 155 MB/s
[ perf record: Woken up 3 times to write data ]
[ perf record: Captured and wrote 0.884 MB perf.data (~38630 samples) ]

# perf report
Events: 22K
cycles                                                              
 40,14%  dd  [kernel.kallsyms]  [k] copy_user_generic_string
  3,12%  dd  [kernel.kallsyms]  [k] native_read_tsc
  3,00%  dd  [kernel.kallsyms]  [k] put_page
  2,98%  dd  [kernel.kallsyms]  [k] iowrite8
  2,04%  dd  [kernel.kallsyms]  [k] get_page_from_freelist
  1,87%  dd  [kernel.kallsyms]  [k] delay_tsc
  1,77%  dd  [kernel.kallsyms]  [k] kmem_cache_alloc
  1,69%  dd  [kernel.kallsyms]  [k] __mem_cgroup_commit_charge
  1,52%  dd  [kernel.kallsyms]  [k] submit_bh
  1,38%  dd  [kernel.kallsyms]  [k] ioread8
  1,32%  dd  [kernel.kallsyms]  [k] __rmqueue
  1,29%  dd  [kernel.kallsyms]  [k] block_read_full_page
  1,28%  dd  [kernel.kallsyms]  [k] __ticket_spin_lock
  1,23%  dd  [kernel.kallsyms]  [k] __slab_alloc
  1,15%  dd  [kernel.kallsyms]  [k] file_read_actor
  0,85%  dd  [kernel.kallsyms]  [k] generic_make_request.part.51
  0,84%  dd  [kernel.kallsyms]  [k] __alloc_pages_nodemask
  0,82%  dd  [kernel.kallsyms]  [k] create_empty_buffers
  0,81%  dd  [kernel.kallsyms]  [k] get_partial_node
  0,81%  dd  [kernel.kallsyms]  [k] lookup_page_cgroup
  0,78%  dd  [kernel.kallsyms]  [k] mem_cgroup_add_lru_list.part.45
  0,72%  dd  [kernel.kallsyms]  [k] ____pagevec_lru_add_fn

# echo 3 >/proc/sys/vm/drop_caches ;perf record dd if=/dev/sda
of=/dev/null bs=1M count=4096
4096+0 enregistrements lus
4096+0 enregistrements écrits
4294967296 octets (4,3 GB) copiés, 25,8117 s, 166 MB/s
[ perf record: Woken up 3 times to write data ]
[ perf record: Captured and wrote 0.810 MB perf.data (~35398 samples) ]

# perf report
Events: 20K
cycles                                                              
 31,91%  dd  [kernel.kallsyms]  [k] copy_user_generic_string
  3,87%  dd  [kernel.kallsyms]  [k] native_read_tsc
  3,58%  dd  [kernel.kallsyms]  [k] iowrite8
  2,43%  dd  [kernel.kallsyms]  [k] put_page
  2,30%  dd  [kernel.kallsyms]  [k] delay_tsc
  2,09%  dd  [kernel.kallsyms]  [k] get_page_from_freelist
  1,96%  dd  [kernel.kallsyms]  [k] __mem_cgroup_commit_charge
  1,79%  dd  [kernel.kallsyms]  [k] submit_bh
  1,75%  dd  [kernel.kallsyms]  [k] kmem_cache_alloc
  1,74%  dd  [kernel.kallsyms]  [k] ioread8
  1,68%  dd  [kernel.kallsyms]  [k] block_read_full_page
  1,62%  dd  [kernel.kallsyms]  [k] __ticket_spin_lock
  1,38%  dd  [kernel.kallsyms]  [k] __rmqueue
  1,12%  dd  [kernel.kallsyms]  [k] create_empty_buffers
  1,08%  dd  [kernel.kallsyms]  [k] __slab_alloc
  1,07%  dd  [kernel.kallsyms]  [k] file_read_actor
  1,06%  dd  [kernel.kallsyms]  [k] generic_make_request.part.51
  0,94%  dd  [kernel.kallsyms]  [k] lookup_page_cgroup
  0,85%  dd  [kernel.kallsyms]  [k] __alloc_pages_nodemask
  0,85%  dd  [kernel.kallsyms]  [k] find_get_page
  0,83%  dd  [kernel.kallsyms]  [k] __lru_cache_add
  0,81%  dd  [kernel.kallsyms]  [k] add_to_page_cache_locked.part.29


# echo 3 >/proc/sys/vm/drop_caches ;perf record dd if=/dev/sda
of=/dev/null bs=128k count=32768
32768+0 enregistrements lus
32768+0 enregistrements écrits
4294967296 octets (4,3 GB) copiés, 19,6924 s, 218 MB/s
[ perf record: Woken up 3 times to write data ]
[ perf record: Captured and wrote 0.961 MB perf.data (~41992 samples) ]

# perf report
 29,85%  dd  [kernel.kallsyms]  [k] copy_user_generic_string
  2,61%  dd  [kernel.kallsyms]  [k] __mem_cgroup_commit_charge
  2,53%  dd  [kernel.kallsyms]  [k] get_page_from_freelist
  2,27%  dd  [kernel.kallsyms]  [k] block_read_full_page
  1,99%  dd  [kernel.kallsyms]  [k] __ticket_spin_lock
  1,81%  dd  [kernel.kallsyms]  [k] kmem_cache_alloc
  1,65%  dd  [kernel.kallsyms]  [k] file_read_actor
  1,60%  dd  [kernel.kallsyms]  [k] __rmqueue
  1,58%  dd  [kernel.kallsyms]  [k] put_page
  1,51%  dd  [kernel.kallsyms]  [k] submit_bh
  1,37%  dd  [kernel.kallsyms]  [k] create_empty_buffers
  1,30%  dd  [kernel.kallsyms]  [k] generic_make_request.part.51
  1,09%  dd  [kernel.kallsyms]  [k] __alloc_pages_nodemask
  1,06%  dd  [kernel.kallsyms]  [k] do_generic_file_read.constprop.35
  1,01%  dd  [kernel.kallsyms]  [k] lookup_page_cgroup
  1,00%  dd  [kernel.kallsyms]  [k] add_to_page_cache_locked.part.29
  0,93%  dd  [kernel.kallsyms]  [k] find_get_page
  0,92%  dd  [kernel.kallsyms]  [k] blk_rq_map_sg
  0,92%  dd  [kernel.kallsyms]  [k] radix_tree_insert
  0,89%  dd  [kernel.kallsyms]  [k] alloc_pages_current
  0,88%  dd  [kernel.kallsyms]  [k] mem_cgroup_add_lru_list.part.45
  0,88%  dd  [kernel.kallsyms]  [k] radix_tree_lookup_element




  reply	other threads:[~2012-01-30  5:32 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27  6:00 Bad SSD performance with recent kernels Herbert Poetzl
2012-01-27  6:44 ` Eric Dumazet
2012-01-28 12:51 ` Wu Fengguang
2012-01-28 13:33   ` Eric Dumazet
2012-01-29  5:59     ` Wu Fengguang
2012-01-29  8:42       ` Herbert Poetzl
2012-01-29  9:28         ` Wu Fengguang
2012-01-29 10:03       ` Eric Dumazet
2012-01-29 11:16         ` Wu Fengguang
2012-01-29 13:13           ` Eric Dumazet
2012-01-29 15:52             ` Pádraig Brady
2012-01-29 16:10             ` Wu Fengguang
2012-01-29 20:15               ` Herbert Poetzl
2012-01-30 11:18                 ` Wu Fengguang
2012-01-30 12:34                   ` Eric Dumazet
2012-01-30 14:01                     ` Wu Fengguang
2012-01-30 14:05                       ` Wu Fengguang
2012-01-30  3:17               ` Shaohua Li
2012-01-30  5:31                 ` Eric Dumazet [this message]
2012-01-30  5:45                   ` Shaohua Li
2012-01-30  7:13                 ` Herbert Poetzl
2012-01-30  7:22                   ` Shaohua Li
2012-01-30  7:36                     ` Herbert Poetzl
2012-01-30  8:12                       ` Shaohua Li
2012-01-30 10:31                         ` Shaohua Li
2012-01-30 14:28                           ` Wu Fengguang
2012-01-30 14:51                             ` Eric Dumazet
2012-01-30 22:26                               ` Vivek Goyal
2012-01-31  0:14                                 ` Shaohua Li
2012-01-31  1:07                                   ` Wu Fengguang
2012-01-31  3:00                                     ` Shaohua Li
2012-01-31  2:17                                 ` Eric Dumazet
2012-01-31  8:46                                 ` Eric Dumazet
2012-01-31  6:36                             ` Herbert Poetzl
2012-01-30 14:48         ` Wu Fengguang
2012-01-28 17:01   ` Herbert Poetzl

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=1327901519.2891.4.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=herbert@13thfloor.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaohua.li@intel.com \
    --cc=tj@kernel.org \
    --cc=wfg@linux.intel.com \
    /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).