From: Mark Hemment <markhe@veritas.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Linus Torvalds <torvalds@transmeta.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Align VM locks
Date: Thu, 16 Aug 2001 19:44:04 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.33.0108161933240.3340-100000@alloc.wat.veritas.com> (raw)
In-Reply-To: <20010816202606.B8726@athlon.random>
On Thu, 16 Aug 2001, Andrea Arcangeli wrote:
> BTW, for your other patch you sent a few hours ago you forgot to drop
> the KMAP entry that is wasting NR_CPUS*PAGE_SIZE of virtual address
> space:
>
> ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.8aa1/00_create_bounces-sleeps-1
Eh, no I didn't.
At least on the work load I'm interest in, SpecFS v2.0 over NFSv3,
removing the KM_BOUNCE_WRITE results in a performance drop (confirmed
today).
It is often the case that when it comes time to write a page out it has
lost any mapping it had when it was made dirty via a write(), so there is
no side benefit of using a straight kmap().
By having KM_BOUNCE_WRITE we don't run through the "normal" mapping
space on I/O. Not having KM_BOUNCE_WRITE causing extra shootdowns, which
_are_ expensive, as the code needs to busy-wait for all the other engines
(while the kmap_lock held - and on a 4-way there is a good chance one of
the processors is running with interrupts disabled).
KM_BOUNCE_WRITE may waste virtual address-space, but it saves on
expensive shootdowns.
Mark
next prev parent reply other threads:[~2001-08-16 18:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-16 17:41 Mark Hemment
2001-08-16 18:26 ` Andrea Arcangeli
2001-08-16 18:44 ` Mark Hemment [this message]
2001-08-16 18:52 ` Andrea Arcangeli
2001-08-16 18:57 ` Andrea Arcangeli
2001-08-16 19:46 ` Mark Hemment
2001-08-16 20:27 ` Ben LaHaise
2001-08-16 23:35 ` Andrea Arcangeli
2001-08-16 19:14 ` Andrew Morton
2001-08-16 23:33 ` Andrea Arcangeli
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=Pine.LNX.4.33.0108161933240.3340-100000@alloc.wat.veritas.com \
--to=markhe@veritas.com \
--cc=andrea@suse.de \
--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®