From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Jianbo Liu <jianbo.liu@linaro.org>
Cc: dev@dpdk.org, thomas@monjalon.net,
Hemant Agrawal <hemant.agrawal@nxp.com>,
christian.ehrhardt@canonical.com
Subject: Re: [dpdk-dev] [PATCH] config: set cache line as 128B in the generic arm64 config
Date: Fri, 28 Apr 2017 10:33:00 +0530 [thread overview]
Message-ID: <20170428050259.GA3912@jerin> (raw)
In-Reply-To: <CAP4Qi39OGHq8fhmFDqQBsSuU8=w5Trsb0R-=tcJm2GNgKEGcig@mail.gmail.com>
-----Original Message-----
> Date: Fri, 28 Apr 2017 10:14:11 +0800
> From: Jianbo Liu <jianbo.liu@linaro.org>
> To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> Cc: dev@dpdk.org, thomas@monjalon.net, Hemant Agrawal
> <hemant.agrawal@nxp.com>, christian.ehrhardt@canonical.com
> Subject: Re: [dpdk-dev] [PATCH] config: set cache line as 128B in the
> generic arm64 config
>
> On 27 April 2017 at 00:29, Jerin Jacob <jerin.jacob@caviumnetworks.com> wrote:
> > armv8 implementations may have 64B or 128B cache line.
> > Setting to the maximum available cache line size in generic config to
> > address minimum DMA alignment across all arm64 implementations.
> >
> > Increasing the cacheline size has no negative impact to cache invalidation
> > on systems with a smaller cache line.
> >
> > The need for the minimum DMA alignment has impact on functional aspects
> > of the platform so default config should cater the functional aspects.
> >
> > There is an impact on memory usage with this scheme, but that's not too
> > important for the single image arm64 distribution use case.
> >
> > The arm64 linux kernel followed the similar approach for single
> > arm64 image use case.
> > http://lxr.free-electrons.com/source/arch/arm64/include/asm/cache.h
> >
> > Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> > ---
> > config/defconfig_arm64-armv8a-linuxapp-gcc | 5 +++++
> > config/defconfig_arm64-dpaa2-linuxapp-gcc | 1 +
> > config/defconfig_arm64-xgene1-linuxapp-gcc | 1 +
> > 3 files changed, 7 insertions(+)
> > --
>
> Acked-by: Jianbo Liu <jianbo.liu@linaro.org>
Thomas,
Is it possible to merge this patch for v17.05-rc3?
next prev parent reply other threads:[~2017-04-28 5:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 16:29 Jerin Jacob
2017-04-28 2:14 ` Jianbo Liu
2017-04-28 5:03 ` Jerin Jacob [this message]
2017-04-30 21:10 ` Thomas Monjalon
2017-04-28 3:59 ` santosh
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=20170428050259.GA3912@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jianbo.liu@linaro.org \
--cc=thomas@monjalon.net \
/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).