From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: whiteheadm-HInyCGIudOg@public.gmane.org
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>,
konrad.wilk-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH] x86: enable swiotlb for > 4GiG ram on 32-bit kernels
Date: Wed, 17 Oct 2018 18:33:51 +0200 [thread overview]
Message-ID: <20181017163351.GA23719@lst.de> (raw)
In-Reply-To: <CAP8WD_Zj5aMcTCVtV-hot3zLNfNuMzHyeogm0Lqb=+XZ1LdkKw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Tue, Oct 16, 2018 at 09:11:09AM -0400, tedheadster wrote:
> Christoph,
> this fix has causes performance to decrease dramatically. Kernel
> builds that used to take 10-15 minutes are now taking 45-60 minutes on
> the same machine.
What is the comparism? Is this on a non-aic7xxx kernel with and without
the fix?
next prev parent reply other threads:[~2018-10-17 16:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-14 7:52 [PATCH] x86: enable swiotlb for > 4GiG ram on 32-bit kernels Christoph Hellwig
[not found] ` <20181014075208.2715-1-hch-jcswGhMUV9g@public.gmane.org>
2018-10-14 8:13 ` Thomas Gleixner
[not found] ` <alpine.DEB.2.21.1810141012510.1438-ecDvlHI5BZPZikZi3RtOZ1XZhhPuCNm+@public.gmane.org>
2018-10-14 8:14 ` Christoph Hellwig
[not found] ` <20181014081443.GA17889-jcswGhMUV9g@public.gmane.org>
2018-10-14 8:57 ` Thomas Gleixner
[not found] ` <alpine.DEB.2.21.1810141055440.1438-ecDvlHI5BZPZikZi3RtOZ1XZhhPuCNm+@public.gmane.org>
2018-10-14 9:04 ` Ingo Molnar
2018-10-14 12:49 ` tedheadster
2018-10-15 18:52 ` Konrad Rzeszutek Wilk
2018-10-16 13:11 ` tedheadster
[not found] ` <CAP8WD_Zj5aMcTCVtV-hot3zLNfNuMzHyeogm0Lqb=+XZ1LdkKw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-10-17 10:16 ` Thomas Gleixner
2018-10-17 16:33 ` Christoph Hellwig [this message]
[not found] ` <20181017163351.GA23719-jcswGhMUV9g@public.gmane.org>
2018-10-17 17:41 ` tedheadster
[not found] ` <CAP8WD_boL-DxEXxa-ci382Ff8yTdMS9T+sy2Y0-LEX-WPc8L_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-10-18 12:51 ` Christoph Hellwig
[not found] ` <20181018125116.GA24676-jcswGhMUV9g@public.gmane.org>
2018-10-19 1:00 ` tedheadster
[not found] ` <CAP8WD_Z2XvLsqimSnODwr5gj6GRuzh4SMKN56n6Y0JzufG=E8A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-10-19 5:51 ` Ingo Molnar
2018-10-18 6:12 ` Ingo Molnar
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=20181017163351.GA23719@lst.de \
--to=hch-jcswghmuv9g@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=konrad.wilk-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=whiteheadm-HInyCGIudOg@public.gmane.org \
--cc=x86-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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;
as well as URLs for NNTP newsgroup(s).