Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Peter Jones <pjones@redhat.com>, Dave Airlie <airlied@redhat.com>,
	Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Andy Lutomirski <luto@kernel.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] efifb: allow user to disable write combined mapping.
Date: Mon, 31 Jul 2017 17:10:19 +0000	[thread overview]
Message-ID: <9159891.uf5zLSyfMh@amdc3058> (raw)
In-Reply-To: <3242167.nzKsUOiBJb@amdc3058>

On Tuesday, July 25, 2017 10:56:15 AM Bartlomiej Zolnierkiewicz wrote:
> On Tuesday, July 25, 2017 02:00:00 PM Dave Airlie wrote:
> > On 19 July 2017 at 00:34, Peter Jones <pjones@redhat.com> wrote:
> > > On Tue, Jul 18, 2017 at 04:09:09PM +1000, Dave Airlie wrote:
> > >> This patch allows the user to disable write combined mapping
> > >> of the efifb framebuffer console using an nowc option.
> > >>
> > >> A customer noticed major slowdowns while logging to the console
> > >> with write combining enabled, on other tasks running on the same
> > >> CPU. (10x or greater slow down on all other cores on the same CPU
> > >> as is doing the logging).
> > >>
> > >> I reproduced this on a machine with dual CPUs.
> > >> Intel(R) Xeon(R) CPU E5-2609 v3 @ 1.90GHz (6 core)
> > >>
> > >> I wrote a test that just mmaps the pci bar and writes to it in
> > >> a loop, while this was running in the background one a single
> > >> core with (taskset -c 1), building a kernel up to init/version.o
> > >> (taskset -c 8) went from 13s to 133s or so. I've yet to explain
> > >> why this occurs or what is going wrong I haven't managed to find
> > >> a perf command that in any way gives insight into this.
> > >>
> > >>     11,885,070,715      instructions              #    1.39  insns per cycle
> > >> vs
> > >>     12,082,592,342      instructions              #    0.13  insns per cycle
> > >>
> > >> is the only thing I've spotted of interest, I've tried at least:
> > >> dTLB-stores,dTLB-store-misses,L1-dcache-stores,LLC-store,LLC-store-misses,LLC-load-misses,LLC-loads,\mem-loads,mem-stores,iTLB-loads,iTLB-load-misses,cache-references,cache-misses
> > >>
> > >> For now it seems at least a good idea to allow a user to disable write
> > >> combining if they see this until we can figure it out.
> > >
> > > Well, that's kind of amazing, given 3c004b4f7eab239e switched us /to/
> > > using ioremap_wc() for the exact same reason.  I'm not against letting
> > > the user force one way or the other if it helps, though it sure would be
> > > nice to know why.
> > >
> > > Anyway,
> > >
> > > Acked-By: Peter Jones <pjones@redhat.com>
> > >
> > > Bartlomiej, do you want to handle this in your devel tree?
> > 
> > I'm happy to stick this in a drm-fixes pull with this ack.
> 
> I'll put it into fbdev fixes for 4.13 with other fbdev patches.

Patch queued for 4.13, thanks.

Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics


      reply	other threads:[~2017-07-31 17:10 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
2017-07-25  4:00   ` Dave Airlie
2017-07-25  8:56     ` Bartlomiej Zolnierkiewicz
2017-07-31 17:10       ` Bartlomiej Zolnierkiewicz [this message]

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=9159891.uf5zLSyfMh@amdc3058 \
    --to=b.zolnierkie@samsung.com \
    --cc=airlied@gmail.com \
    --cc=airlied@redhat.com \
    --cc=hpa@zytor.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 \
    /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