From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mm: implement no-highmem fast path in kmap_atomic_pfn()
Date: Tue, 22 Jul 2014 20:41:09 -0300 [thread overview]
Message-ID: <20140722234109.GA21545@arch.cereza> (raw)
In-Reply-To: <1404305055-16769-1-git-send-email-thomas.petazzoni@free-electrons.com>
On 02 Jul 02:44 PM, Thomas Petazzoni wrote:
> Since CONFIG_HIGHMEM got enabled on ARMv5 Kirkwood, we have noticed a
> very significant drop in networking performance. The test were
> conducted on an OpenBlocks A7 board. Without this patch, the outgoing
> performance measured with iperf are:
>
> - highmem OFF, TSO OFF 544 Mbit/s
> - highmem OFF, TSO ON 942 Mbit/s
> - highmem ON, TSO OFF 306 Mbit/s
> - highmem ON, TSO ON 246 Mbit/s
>
> On this Kirkwood platform, the L2 cache is a Feroceon cache, and with
> this cache, all the range operations have to be done on virtual
> addresses and not physical addresses. Therefore, whenever
> CONFIG_HIGHMEM is enabled, the cache maintenance operations call
> kmap_atomic_pfn() and kunmap_atomic().
>
> However, kmap_atomic_pfn() does not implement the same fast path for
> non-highmem pages as the one implemented in kmap_atomic(), and this is
> one of the reason for the performance drop. While this patch does not
> fully restore the performances, it clearly improves them a lot:
>
> without patch with patch
>
> - highmem ON, TSO OFF 306 Mbit/s 387 Mbit/s
> - highmem ON, TSO ON 246 Mbit/s 434 Mbit/s
>
> We're still far from the !CONFIG_HIGHMEM performances, but it does
> improve a bit the situation.
>
> Thanks a lot to Ezequiel Garcia and Gregory Clement for all the
> testing work around this topic.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> arch/arm/mm/highmem.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/arm/mm/highmem.c b/arch/arm/mm/highmem.c
> index 45aeaac..e17ed00 100644
> --- a/arch/arm/mm/highmem.c
> +++ b/arch/arm/mm/highmem.c
> @@ -127,8 +127,11 @@ void *kmap_atomic_pfn(unsigned long pfn)
> {
> unsigned long vaddr;
> int idx, type;
> + struct page *page = pfn_to_page(pfn);
>
> pagefault_disable();
> + if (!PageHighMem(page))
> + return page_address(page);
>
> type = kmap_atomic_idx_push();
> idx = type + KM_TYPE_NR * smp_processor_id();
What's the status of this one?
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
prev parent reply other threads:[~2014-07-22 23:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 12:44 [PATCH] ARM: mm: implement no-highmem fast path in kmap_atomic_pfn() Thomas Petazzoni
2014-07-22 23:41 ` Ezequiel Garcia [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=20140722234109.GA21545@arch.cereza \
--to=ezequiel.garcia@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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