From: Catalin Marinas <catalin.marinas@arm.com>
To: David Clear <dac2@pensando.io>
Cc: will@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: ARM64: Question: Supporting outer-no-allocate
Date: Thu, 30 Jul 2020 12:40:08 +0100 [thread overview]
Message-ID: <20200730114007.GI25149@gaia> (raw)
In-Reply-To: <CA+nMikHSH9JTEcB_h1rVXRP-NoHDdpG4q32DAvBc8V78zTEq=g@mail.gmail.com>
On Fri, Jul 17, 2020 at 03:24:31PM -0700, David Clear wrote:
> I'd like to ask whether we can support the configuration of the TCR and MAIR
> registers so as to select outer read-no-allocate, outer write-no-allocate on
> ARM memory transactions. I recognize that this might be quite a limited
> use-case so let me explain why I'm asking.
>
> The Pensando ASIC is a PCIE host-attached multi-100Gbps I/O chip that includes
> an A72 arm64 complex for internal device management. The hardware data-path
> makes extensive use of RAM for in-flight metadata, and performance is
> maximized by preventing the ARM from allocating cache lines in L3 that would
> evict that metadata, at the acceptable cost of increasing ARM memory latency
> through L3.
>
> I'd like to upstream as much support for the chip as possible, but I don't
> want to formally post a patch if the idea is objectionable, or if there's
> a more acceptable way to accomplish the same goal.
>
> The simplest solution might be a new Kconfig option MMU_OUTER_NO_ALLOCATE
> to choose the desired TCR and MAIR values:
>
> arch/arm64/include/asm/sysreg.h:
> #ifndef CONFIG_MMU_OUTER_NO_ALLOCATE
> #define MAIR_ATTR_NORMAL_WT UL(0x8b)
> #define MAIR_ATTR_NORMAL UL(0xcf)
> #else
> #define MAIR_ATTR_NORMAL_WT UL(0xbb)
> #define MAIR_ATTR_NORMAL UL(0xff)
> #endif
I'm not keen on having config options for such use-cases. In theory, we
could add a command-line option but given that it's only for one driver
that's not even in mainline, it doesn't have a strong case ;).
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2020-07-30 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 22:24 ARM64: Question: Supporting outer-no-allocate David Clear
2020-07-30 11:40 ` Catalin Marinas [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=20200730114007.GI25149@gaia \
--to=catalin.marinas@arm.com \
--cc=dac2@pensando.io \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).