From: "Stephen C. Tweedie" <sct@redhat.com>
To: lord@sgi.com
Cc: "Benjamin C.R. LaHaise" <blah@kvack.org>,
David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: kmap_kiobuf()
Date: Wed, 28 Jun 2000 19:06:12 +0100 [thread overview]
Message-ID: <20000628190612.E2392@redhat.com> (raw)
In-Reply-To: <200006281652.LAA19162@jen.americas.sgi.com>; from lord@sgi.com on Wed, Jun 28, 2000 at 11:52:40AM -0500
Hi,
On Wed, Jun 28, 2000 at 11:52:40AM -0500, lord@sgi.com wrote:
>
> I am not a VM guy either, Ben, is the cost of the TLB flush mostly in
> the synchronization between CPUs, or is it just expensive anyway you
> look at it?
The TLB IPI is by far the biggest factor here.
--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-06-28 18:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-28 16:52 kmap_kiobuf() lord
2000-06-28 18:06 ` Stephen C. Tweedie [this message]
2000-06-28 19:06 ` kmap_kiobuf() Manfred Spraul
2000-06-28 21:05 ` kmap_kiobuf() Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2000-06-28 20:16 kmap_kiobuf() lord
2000-06-28 21:22 ` kmap_kiobuf() Benjamin C.R. LaHaise
2000-06-29 9:34 ` kmap_kiobuf() Stephen C. Tweedie
2000-06-29 13:45 ` kmap_kiobuf() Steve Lord
2000-06-28 15:54 kmap_kiobuf() lord
2000-06-28 16:06 ` kmap_kiobuf() David Woodhouse
2000-06-28 16:24 ` kmap_kiobuf() Benjamin C.R. LaHaise
2000-06-28 18:07 ` kmap_kiobuf() Stephen C. Tweedie
2000-06-28 18:45 ` kmap_kiobuf() David Woodhouse
2000-06-29 9:09 ` kmap_kiobuf() Stephen C. Tweedie
2000-06-28 17:46 ` kmap_kiobuf() Stephen C. Tweedie
2000-06-28 15:41 kmap_kiobuf() David Woodhouse
2000-06-28 17:44 ` kmap_kiobuf() Stephen C. Tweedie
2000-06-29 10:52 ` kmap_kiobuf() Stephen C. Tweedie
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=20000628190612.E2392@redhat.com \
--to=sct@redhat.com \
--cc=blah@kvack.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=lord@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.