From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: Linus Torvalds <torvalds@transmeta.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch 5/21] pagevec infrastructure
Date: Wed, 14 Aug 2002 01:41:12 -0700 [thread overview]
Message-ID: <20020814084112.GP15685@holomorphy.com> (raw)
In-Reply-To: <3D561482.AC248312@zip.com.au>
On Sun, Aug 11, 2002 at 12:38:42AM -0700, Andrew Morton wrote:
> This is the first patch in a series of eight which address
> pagemap_lru_lock contention, and which simplify the VM locking
> hierarchy.
> Most testing has been done with all eight patches applied, so it would
> be best not to cherrypick, please.
dbench 256 on a 16x/16G numaq:
Throughput 50.3639 MB/sec (NB=62.9549 MB/sec 503.639 MBit/sec) 256 procs
c013c444 7514467 78.18 .text.lock.highmem
c013baac 584912 6.08539 kmap_high
c013bca0 556734 5.79223 kunmap_high
c012f260 133797 1.39202 generic_file_write
c012e53c 85433 0.88884 file_read_actor
c0114820 72361 0.752839 scheduler_tick
c01441ec 61757 0.642516 block_prepare_write
c013c18c 46977 0.488746 blk_queue_bounce
c0105394 46657 0.485417 default_idle
c01113b8 37263 0.387682 smp_apic_timer_interrupt
c0135afc 35618 0.370567 rmqueue
c014380c 26328 0.273915 __block_prepare_write
c012dec0 19238 0.200151 unlock_page
c01405f4 17391 0.180935 vfs_write
c01433e8 17382 0.180841 create_empty_buffers
c01361d8 16797 0.174755 page_cache_release
c01143d8 16727 0.174027 load_balance
c0136632 16378 0.170396 .text.lock.page_alloc
c013ba28 12628 0.131381 flush_all_zero_pkmaps
c013429c 10114 0.105225 lru_cache_add
c016de8c 9700 0.100918 ext2_prepare_write
c0135820 7610 0.079174 __free_pages_ok
prev parent reply other threads:[~2002-08-14 8:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-11 7:38 Andrew Morton
2002-08-14 8:41 ` William Lee Irwin III [this message]
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=20020814084112.GP15685@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®