mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ian Godin <Ian.Godin@lowrydigital.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Drive performance bottleneck
Date: Thu, 3 Feb 2005 08:49:42 -0800	[thread overview]
Message-ID: <1e90ea5b2039243539df074d7bc9a658@lowrydigital.com> (raw)
In-Reply-To: <E1CwY6U-0003p6-00@calista.eckenfels.6bone.ka-ip.net>

On Feb 2, 2005, at 7:56 PM, Bernd Eckenfels wrote:

> In article <c4fc982390674caa2eae4f252bf4fc78@lowrydigital.com> you 
> wrote:
>>  Below is an oprofile (truncated) of (the same) dd running on 
>> /dev/sdb.
>
> do  you also have the oprofile of the sg_dd handy?
>
> Greetings
> Bernd
>

   Just ran it on the sg_dd (using /dev/sg1):

CPU: P4 / Xeon, speed 3402.13 MHz (estimated)
Counted GLOBAL_POWER_EVENTS events (time during which processor is not 
stopped) with a unit mask of 0x01 (mandatory) count 10
0000
samples  %        symbol name
2145136  89.7474  __copy_to_user_ll
64720     2.7077  lock_kernel
17883     0.7482  mark_offset_tsc
16212     0.6783  page_address
8091      0.3385  schedule
5380      0.2251  timer_interrupt
5314      0.2223  _spin_lock
5311      0.2222  mwait_idle
4034      0.1688  sysenter_past_esp
3569      0.1493  do_anonymous_page
3530      0.1477  apic_timer_interrupt
3368      0.1409  _spin_lock_irqsave
3150      0.1318  sg_read_xfer
3043      0.1273  kmem_cache_alloc
2590      0.1084  find_busiest_group
2553      0.1068  scheduler_tick
2319      0.0970  __copy_from_user_ll
2299      0.0962  sg_ioctl
2131      0.0892  irq_entries_start
1905      0.0797  sys_ioctl
1773      0.0742  copy_page_range
1678      0.0702  fget
1648      0.0689  __switch_to
1648      0.0689  scsi_block_when_processing_errors
1632      0.0683  sg_start_req
1569      0.0656  increment_tail
1511      0.0632  try_to_wake_up
1506      0.0630  update_one_process
1454      0.0608  fput
1397      0.0584  do_gettimeofday
1396      0.0584  zap_pte_range
1371      0.0574  recalc_task_prio
1357      0.0568  sched_clock
1352      0.0566  sg_link_reserve
1282      0.0536  __elv_add_request
1229      0.0514  kmap_atomic
1195      0.0500  page_fault

   Oddly enough it appears to also be copying to user space...

      Ian.


  reply	other threads:[~2005-02-03 16:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-03  2:24 Ian Godin
2005-02-03  3:56 ` Bernd Eckenfels
2005-02-03 16:49   ` Ian Godin [this message]
2005-02-03 16:06 ` Jens Axboe
2005-02-03 17:40 ` Nuno Silva
2005-02-03 18:08   ` Ian Godin
2005-02-03 19:03     ` Paulo Marques
2005-02-04 19:36       ` Andy Isaacson
2005-02-04  9:32 ` Andrew Morton
2005-02-04 22:51   ` Lincoln Dale
2005-02-04 23:07     ` Andrew Morton
2005-02-06  4:25       ` Nuno Silva

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=1e90ea5b2039243539df074d7bc9a658@lowrydigital.com \
    --to=ian.godin@lowrydigital.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

Powered by JetHome