From: "H. Peter Anvin" <hpa@zytor.com>
To: Dave Airlie <airlied@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Jones <pjones@redhat.com>,
the arch/x86 maintainers <x86@kernel.org>,
Dave Airlie <airlied@redhat.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Lutomirski <luto@kernel.org>
Subject: Re: [PATCH] efifb: allow user to disable write combined mapping.
Date: Mon, 31 Jul 2017 12:13:32 -0700 [thread overview]
Message-ID: <487000e3-afeb-0e59-c563-0ef4b1347d8d@zytor.com> (raw)
In-Reply-To: <CAPM=9tyWv79U9=-YNacf34don_Gn5RGggBsZG7R9FNuV8_qe1g@mail.gmail.com>
On 07/18/17 13:44, Dave Airlie wrote:
>
> In normal operation the console is faster with _wc. It's the side effects
> on other cores that is the problem.
>
I'm guessing leaving these as UC- rate-limits them so it doesn't
interfere with the I/O operations on the other cores...
-hpa
next prev parent reply other threads:[~2017-07-31 19:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 6:09 [PATCH] efifb: allow user to disable write combined mapping Dave Airlie
2017-07-18 14:34 ` Peter Jones
2017-07-18 19:57 ` Linus Torvalds
2017-07-18 20:44 ` Dave Airlie
2017-07-18 21:21 ` Dave Airlie
2017-07-18 22:22 ` Linus Torvalds
2017-07-18 23:16 ` Dave Airlie
2017-07-18 23:16 ` Dave Airlie
2017-07-19 0:00 ` Dave Airlie
2017-07-19 1:15 ` Linus Torvalds
2017-07-20 4:07 ` Dave Airlie
2017-07-20 4:28 ` Andy Lutomirski
2017-07-20 4:44 ` Linus Torvalds
2017-07-21 4:27 ` Dave Airlie
2017-07-20 10:20 ` Ingo Molnar
2017-07-31 19:13 ` H. Peter Anvin [this message]
2017-07-25 4:00 ` Dave Airlie
2017-07-25 8:56 ` Bartlomiej Zolnierkiewicz
2017-07-31 17:10 ` Bartlomiej Zolnierkiewicz
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=487000e3-afeb-0e59-c563-0ef4b1347d8d@zytor.com \
--to=hpa@zytor.com \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=b.zolnierkie@samsung.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=pjones@redhat.com \
--cc=torvalds@linux-foundation.org \
--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