From: Ralf Baechle <ralf@linux-mips.org>
To: Hillf Danton <dhillf@gmail.com>
Cc: David Daney <david.daney@cavium.com>, linux-mips@linux-mips.org
Subject: Re: [PATCH] MIPS: Add fast get_user_pages
Date: Fri, 4 Nov 2011 15:16:03 +0000 [thread overview]
Message-ID: <20111104151603.GB13043@linux-mips.org> (raw)
In-Reply-To: <CAJd=RBC=_+qAnbTaYXgTOoiVdfgppRt-rBs4cnKoZKxHD14nuw@mail.gmail.com>
On Fri, Oct 28, 2011 at 09:26:23PM +0800, Hillf Danton wrote:
When we were chasing the TLB crash recently for a while I was suspecting
the default get_user_fast implementation so I ported gup.c from x86 but I
never really finished it, so thanks for ridding me of one item from my
to do list.
This probably wants some more testing in particular on 32-bit systems with
64-bit pagetables such as some Alchemy configurations or 32-bit kernels
on Sibyte systems.
I fixed up a reject in arch/mips/mm/Makefile due to whitespace differences
and queued the patch for 3.3.
Have you made any benchmarks of the new gup.c?
Thanks,
Ralf
next prev parent reply other threads:[~2011-11-04 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 13:26 [PATCH] MIPS: Add fast get_user_pages Hillf Danton
2011-11-04 15:16 ` Ralf Baechle [this message]
2011-11-07 12:07 ` Ralf Baechle
2011-11-08 12:17 ` Hillf Danton
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=20111104151603.GB13043@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=david.daney@cavium.com \
--cc=dhillf@gmail.com \
--cc=linux-mips@linux-mips.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