From: "H. Peter Anvin" <h.peter.anvin@intel.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Pauli Nieminen <suokkos@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Venkatesh Pallipadi <venkatesh.pallipadi@gmail.com>,
Suresh Siddha <suresh.b.siddha@intel.com>
Subject: Re: [PATCH 5/7] arch/x86: Add array variants for setting memory to wc caching.
Date: Tue, 18 May 2010 09:43:42 -0700 [thread overview]
Message-ID: <4BF2C3BE.7060804@intel.com> (raw)
In-Reply-To: <AANLkTilyGz86DlwOvtVolthE66VzkSwj9jDv0s138Egi@mail.gmail.com>
On 05/18/2010 02:34 AM, Dave Airlie wrote:
> On Thu, Apr 1, 2010 at 10:45 PM, Pauli Nieminen <suokkos@gmail.com> wrote:
>> Setting single memory pages at a time to wc takes a lot time in cache flush. To
>> reduce number of cache flush set_pages_array_wc and set_memory_array_wc can be
>> used to set multiple pages to WC with single cache flush.
>>
>> This improves allocation performance for wc cached pages in drm/ttm.
>>
>
> I've got this in drm-next for quite a while and almost forgot about
> it, I'm meant to be on holidays and I'd really like to just have Linus
> pull my tree,
>
> I had only one issue with this as we had some problems with doing it
> before but it looks like they've since been fixed in the x86 pat code
> a kernel or two ago so this patch should be fine now.
>
> its been well tested in drm-next on AGP machines by the author,
>
> any objections to this?
>
> Dave.
Acked-by: H. Peter Anvin <hpa@zytor.com>
Go ahead and push it; the patch is straightforward, and the author
(Venki) is reliable.
-hpa
P.S. Please Cc: all the x86 maintainers, not just Ingo.
next prev parent reply other threads:[~2010-05-18 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1270125903-6004-1-git-send-email-suokkos@gmail.com>
[not found] ` <1270125903-6004-5-git-send-email-suokkos@gmail.com>
2010-05-18 9:34 ` Dave Airlie
2010-05-18 16:43 ` H. Peter Anvin [this message]
2010-05-18 20:54 ` Venkatesh Pallipadi
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=4BF2C3BE.7060804@intel.com \
--to=h.peter.anvin@intel.com \
--cc=airlied@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suokkos@gmail.com \
--cc=suresh.b.siddha@intel.com \
--cc=venkatesh.pallipadi@gmail.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
Powered by JetHome