From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Ken Chen <kenchen@google.com>,
Badari Pulavarty <pbadari@gmail.com>,
linux-mm <linux-mm@kvack.org>,
tony.luck@intel.com, Adam Litke <agl@us.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [rfc] lockless get_user_pages for dio (and more)
Date: Wed, 12 Dec 2007 05:11:46 +0000 [thread overview]
Message-ID: <1197436306.6367.12.camel@norville.austin.ibm.com> (raw)
In-Reply-To: <200712121557.20807.nickpiggin@yahoo.com.au>
On Wed, 2007-12-12 at 15:57 +1100, Nick Piggin wrote:
> On Tuesday 11 December 2007 08:30, Dave Kleikamp wrote:
> > Nick,
> > I've played with the fast_gup patch a bit. I was able to find a problem
> > in follow_hugetlb_page() that Adam Litke fixed. I'm haven't been brave
> > enough to implement it on any other architectures, but I did add a
> > default that takes mmap_sem and calls the normal get_user_pages() if the
> > architecture doesn't define fast_gup(). I put it in linux/mm.h, for
> > lack of a better place, but it's a little kludgy since I didn't want
> > mm.h to have to include sched.h. This patch is against 2.6.24-rc4.
> > It's not ready for inclusion yet, of course.
>
> Hi Dave,
>
> Thanks so much. This makes it much more a complete patch (although
> still missing the "normal page" detection).
>
> I think I missed -- or forgot -- what was the follow_hugetlb_page
> problem?
Badari found a problem running some tests and handed it off to me to
look at. I didn't share it publicly. Anyway, we were finding that
fastgup was taking the slow path almost all the time with huge pages.
The problem was that follow_hugetlb_page was failing to fault on a
non-writable page when it needed a writable one. So we'd keep seeing a
non-writable page over and over. This is fixed in 2.6.24-rc5.
> Anyway, I am hoping that someone will one day and test if this and
> find it helps their workload, but on the other hand, if it doesn't
> help anyone then we don't have to worry about adding it to the
> kernel ;) I don't have any real setups that hammers DIO with threads.
> I'm guessing DB2 and/or Oracle does?
I'll try to get someone to run a DB2 benchmark and see what it looks
like.
--
David Kleikamp
IBM Linux Technology Center
--
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-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-12-12 5:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 22:52 [rfc] more granular page table lock for hugepages Siddha, Suresh B
2007-10-09 20:23 ` Ken Chen
2007-10-09 21:05 ` Badari Pulavarty
2007-10-10 0:15 ` Siddha, Suresh B
2007-10-10 6:10 ` Ken Chen
2007-10-10 7:50 ` Ken Chen
2007-10-11 11:39 ` Nick Piggin
2007-10-12 20:34 ` Siddha, Suresh B
2007-10-13 23:27 ` Nick Piggin
2007-10-14 1:01 ` [rfc] lockless get_user_pages for dio (and more) Nick Piggin
2007-10-14 18:19 ` Siddha, Suresh B
2007-10-15 4:15 ` Nick Piggin
2007-10-15 12:25 ` Nick Piggin
2007-10-15 17:03 ` Badari Pulavarty
2007-10-15 17:49 ` Siddha, Suresh B
2007-10-15 17:54 ` Siddha, Suresh B
2007-10-15 20:21 ` Ken Chen
2007-10-16 2:15 ` Nick Piggin
2007-10-16 0:14 ` Dave Hansen
2007-10-16 3:26 ` Nick Piggin
2007-10-16 3:32 ` Nick Piggin
2007-12-10 21:30 ` Dave Kleikamp
2007-12-12 4:57 ` Nick Piggin
2007-12-12 5:11 ` Dave Kleikamp [this message]
2007-12-12 5:40 ` Nick Piggin
2008-01-16 19:58 ` Dave Kleikamp
2008-01-17 6:34 ` Nick Piggin
2008-01-24 7:06 ` Nick Piggin
2007-10-14 15:42 ` [rfc] more granular page table lock for hugepages Siddha, Suresh B
2007-10-15 4:17 ` Nick Piggin
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=1197436306.6367.12.camel@norville.austin.ibm.com \
--to=shaggy@linux.vnet.ibm.com \
--cc=agl@us.ibm.com \
--cc=kenchen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
--cc=pbadari@gmail.com \
--cc=suresh.b.siddha@intel.com \
--cc=tony.luck@intel.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