Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] ext2 vs ext3 on hppa
Date: Fri, 11 Feb 2005 09:53:22 -0700	[thread overview]
Message-ID: <20050211165322.GA8835@colo.lackof.org> (raw)
In-Reply-To: <20050211071629.GA32318@colo.lackof.org>

On Fri, Feb 11, 2005 at 12:16:29AM -0700, Grant Grundler wrote:
> But not for "tar". I can't find the data I collect before. :^(

I found them:
-rw-r--r--  1 root root  33517 Jan  9 21:27 prof-2.6.10-pa6-01
-rw-r--r--  1 root root  23770 Jan 16 19:46 prof-2.6.10-pa6-02

and posted both on
	http://www.parisc-linux.org/~grundler/prof-a500-65/

> ISTR the culprit in ext3 was the bitmap search using atomic ops.
> On parisc, atomic ops are terrible since it requires a spinlock/op/unlock
> sequence.

Yeah, this seems to be right.
I gather this is only an issue for SMP kernels.

grundler <506>sort -rnk 3 prof-2.6.10-pa6-01
 55063 _spin_lock                               1376.5750
 42958 ext3_test_allocatable                     97.6318
  5974 rb_next                                   57.4423
  5541 flush_kernel_icache_page                  55.4100
   800 fdsync                                    40.0000
  1279 flush_user_icache_range_asm               35.5278
 35341 bitmap_search_next_usable_block           30.6780
  1328 _spin_lock_irqsave                        27.6667
  1470 machine_restart                           22.9688
   747 flush_user_dcache_range_asm               20.7500
  1043 cpu_idle                                  14.4861
   135 fisync                                     8.4375
   647 __clear_user_page_asm                      5.7768
...


Sorry - I didn't note exactly which workload the above represented.

And I suspect -02 data is with willy's vma_prev patch applied
that he proposed here:
http://lists.parisc-linux.org/pipermail/parisc-linux/2004-November/025210.html

grundler <509>sort -rnk 3 prof-2.6.10-pa6-02
 61105 _spin_lock                               1527.6250
 43040 ext3_test_allocatable                     97.8182
  4902 rb_next                                   47.1346
 35646 bitmap_search_next_usable_block           30.9427
  2217 flush_kernel_icache_page                  22.1700
   969 _spin_lock_irqsave                        20.1875
  1055 machine_restart                           16.4844
   764 cpu_idle                                  10.6111
   157 fdsync                                     7.8500
   270 flush_user_icache_range_asm                7.5000
   209 flush_user_dcache_range_asm                5.8056
...

hth, 
grant
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  parent reply	other threads:[~2005-02-11 16:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-11  7:16 [parisc-linux] ext2 vs ext3 on hppa Grant Grundler
2005-02-11 13:08 ` Corné Beerse
2005-02-11 17:47   ` Grant Grundler
2005-02-12 20:11     ` Joel Soete
2005-02-11 14:42 ` Matthew Wilcox
2005-02-11 16:53 ` Grant Grundler [this message]
2005-02-11 16:54   ` Matthew Wilcox
2005-02-11 17:18     ` Grant Grundler

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=20050211165322.GA8835@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=parisc-linux@lists.parisc-linux.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