From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] sparc64: Don't pass a pointer to xcall_flush_tlb_pending
Date: Fri, 19 Apr 2013 18:03:37 +0000 [thread overview]
Message-ID: <517186F9.3080500@oracle.com> (raw)
In-Reply-To: <516F0B8A.5070407@oracle.com>
On 04/19/2013 12:41 PM, David Miller wrote:
> From: Dave Kleikamp <dave.kleikamp@oracle.com>
> Date: Fri, 19 Apr 2013 09:46:26 -0500
>
>> Why not pass mm into smp_flush_tlb_page() and use mm_cpumask(mm) as is
>> done in smp_flush_tlb_pending()? I don't see why we wouldn't want to
>> duplicate that logic to avoid cross calls to every cpu for every
>> non-batched flush.
>
> Yes, I noticed that too when doing some tests and fixed that last night.
>
> I also noticed that 2 out of every 3 batch flushes are singletons, so
> I optimized that case. That took a few seconds off of a parallel
> kernel build.
It looks good to me. I'm about to take off for a 3-day vacation, so I
won't be able to rebuild and test this until Tuesday. I don't anticipate
any problems because it is very nearly what I last tested with.
Acked-by: Dave Kleikamp <dave.kleikamp@oracle.com>
>
> We should probably annotate the sparc specific transparent hugepage
> pte loops in arch/sparc/mm/tlb.c with some lazy mmu calls, but I'll
> leave that for another time.
next prev parent reply other threads:[~2013-04-19 18:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 20:52 [PATCH] sparc64: Don't pass a pointer to xcall_flush_tlb_pending Dave Kleikamp
2013-04-17 21:24 ` David Miller
2013-04-17 21:31 ` David Miller
2013-04-17 22:07 ` Dave Kleikamp
2013-04-17 22:44 ` David Miller
2013-04-19 0:51 ` David Miller
2013-04-19 14:46 ` Dave Kleikamp
2013-04-19 17:40 ` Dave Kleikamp
2013-04-19 17:41 ` David Miller
2013-04-19 18:03 ` Dave Kleikamp [this message]
2013-04-19 18:11 ` David Miller
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=517186F9.3080500@oracle.com \
--to=dave.kleikamp@oracle.com \
--cc=sparclinux@vger.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 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.