From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, Andi Kleen <andi@firstfloor.org>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [PATCH 0 of 9] x86/smp function calls: convert x86 tlb flushes to use function calls [POST 2]
Date: Mon, 18 Aug 2008 22:37:29 -0700 [thread overview]
Message-ID: <48AA5C19.3010204@goop.org> (raw)
In-Reply-To: <20080819004531.GI9914@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]
Ingo Molnar wrote:
> nice stuff!
>
> I suspect the extra cost might be worth it for two reasons: 1) we could
> optimize the cross-call implementation further
Unfortunately, I think the kmalloc fix for the RCU issue is going to
hurt quite a lot.
> 2) on systems where TLB
> flushes actually matter, the ability to overlap multiple TLB flushes to
> the same single CPU might improve workloads.
>
...perhaps.
> FYI, i've created a new -tip topic for your patches, tip/x86/tlbflush.
> It's based on tip/irq/sparseirq (there are a good deal of dependencies
> with that topic).
>
Really? I didn't see much conflict when rebasing onto current tip.git.
Just an incidental context conflict in entry_arch.h.
> It would be nice to see some numbers on sufficiently SMP systems, using
> some mmap/munmap intense workload.
I've attached my test program: tlb-mash.c. Compile with "gcc -o
tlb-mash tlb-mash.c -lpthread" and run with ./tlb-mash X, where X is the
number of threads to run (2x cpus works well). It keeps running until
killed, with each thread repeatedly mprotecting a page within a shared
mapping.
J
[-- Attachment #2: tlb-mash.c --]
[-- Type: text/x-csrc, Size: 1210 bytes --]
#include <stdio.h>
#include <pthread.h>
#include <string.h>
#include <unistd.h>
#include <stdlib.h>
#include <sys/mman.h>
#define MAX_THREADS 256
static char *mapping;
static void *masher(void *v)
{
int id = (int)v;
unsigned offset = id * getpagesize();
printf("started thread %d\n", id);
for(;;) {
mprotect(mapping+offset, getpagesize(), PROT_READ);
mprotect(mapping+offset, getpagesize(), PROT_READ | PROT_WRITE);
}
return NULL;
}
int main(int argc, char **argv)
{
int i;
int nthreads = 4;
pthread_t threads[MAX_THREADS];
if (argc == 2) {
int t = atoi(argv[1]);
if (t != 0)
nthreads = t;
}
if (nthreads > MAX_THREADS)
nthreads = MAX_THREADS;
printf("creating %d threads...\n", nthreads);
mapping = mmap(0, getpagesize() * nthreads, PROT_NONE,
MAP_POPULATE|MAP_PRIVATE|MAP_ANONYMOUS, -1, 0);
if (mapping == (char *)-1) {
perror("mmap failed");
return 1;
}
for(i = 0; i < nthreads; i++) {
int ret;
ret = pthread_create(&threads[i], NULL, masher, (void *)i);
if (ret) {
printf("pthread create %d failed: %s\n", i, strerror(ret));
return 1;
}
}
for(i = 0; i < nthreads; i++) {
void *ret;
pthread_join(threads[i], &ret);
}
return 0;
}
next prev parent reply other threads:[~2008-08-19 5:37 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-18 18:23 [PATCH 0 of 9] x86/smp function calls: convert x86 tlb flushes to use function calls [POST 2] Jeremy Fitzhardinge
2008-08-18 18:23 ` [PATCH 1 of 9] x86: put tlb_flush_others() stats in debugfs Jeremy Fitzhardinge
2008-08-18 18:23 ` [PATCH 2 of 9] x86-32: use smp_call_function_mask for SMP TLB invalidations Jeremy Fitzhardinge
2008-08-18 18:23 ` [PATCH 3 of 9] x86-64: " Jeremy Fitzhardinge
2008-08-18 18:23 ` [PATCH 4 of 9] x86: make tlb_32|64 closer Jeremy Fitzhardinge
2008-08-18 18:23 ` [PATCH 5 of 9] x86: unify tlb.c Jeremy Fitzhardinge
2008-08-18 18:23 ` [PATCH 6 of 9] smp_function_call: add multiple queues for scalability Jeremy Fitzhardinge
2008-08-18 18:23 ` [PATCH 7 of 9] x86: add multiple smp_call_function queues Jeremy Fitzhardinge
2008-08-18 18:23 ` [PATCH 8 of 9] x86: make number of smp_call_function queues truely configurable Jeremy Fitzhardinge
2008-08-18 18:23 ` [PATCH 9 of 9] smp function calls: add kernel parameter to disable multiple queues Jeremy Fitzhardinge
2008-08-19 0:45 ` [PATCH 0 of 9] x86/smp function calls: convert x86 tlb flushes to use function calls [POST 2] Ingo Molnar
2008-08-19 1:28 ` Ingo Molnar
2008-08-19 6:18 ` Jeremy Fitzhardinge
2008-08-19 9:27 ` Ingo Molnar
2008-08-19 14:58 ` Jeremy Fitzhardinge
2008-08-19 9:45 ` Peter Zijlstra
2008-08-19 14:58 ` Jeremy Fitzhardinge
2008-08-19 5:37 ` Jeremy Fitzhardinge [this message]
2008-08-19 9:31 ` Ingo Molnar
2008-08-19 9:56 ` Nick Piggin
2008-08-19 10:20 ` Ingo Molnar
2008-08-19 11:08 ` Nick Piggin
2008-08-19 11:44 ` Ingo Molnar
2008-08-19 10:24 ` Ingo Molnar
2008-08-19 10:49 ` Nick Piggin
2008-08-19 10:31 ` Andi Kleen
2008-08-19 11:04 ` Nick Piggin
2008-08-19 11:20 ` Andi Kleen
2008-08-19 7:32 ` Andi Kleen
2008-08-19 7:44 ` Jeremy Fitzhardinge
2008-08-19 7:48 ` Andi Kleen
2008-08-19 8:04 ` Jeremy Fitzhardinge
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=48AA5C19.3010204@goop.org \
--to=jeremy@goop.org \
--cc=andi@firstfloor.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=x86@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