DPDK patches and discussions
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "jerinj@marvell.com" <jerinj@marvell.com>,
	"Gavin Hu (Arm Technology China)" <Gavin.Hu@arm.com>,
	"yskoh@mellanox.com" <yskoh@mellanox.com>
Cc: "russell@mellanox.com" <russell@mellanox.com>,
	"mrosenbluth@mellanox.com" <mrosenbluth@mellanox.com>,
	"dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [EXT] Default cacheline size for ARM
Date: Sat, 5 Jan 2019 22:47:35 +0000	[thread overview]
Message-ID: <AM6PR08MB3672E80CA3555036263E65A5988F0@AM6PR08MB3672.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <0542f8c8cc035433fa4e13cfc23e693f241d5125.camel@marvell.com>

> 
> On Fri, 2019-01-04 at 19:59 +0000, Yongseok Koh wrote:
> > -------------------------------------------------------------------
> > ---
> > Hi,
> >
> > The cacheline size (RTE_CACHE_LINE_SIZE) for ARM CPUs is set to be
> > 128B by default. Mellanox's BlueField is an ARM CPU having Cortex-A72
> > and its CL size is 64B.
Just wondering how many devices are out there with 128B cache line? I also have not heard about any future devices with 128B cache line. If the majority is 64B, why not keep 64B as the default?

> >
> > I can add config/defconfig_arm64-bluefield-linuxapp-gcc for legacy
> > build anyway.
> >
> 
> Makes sense.
> 
> > For the meson build, I know it parses the Main ID register to figure
> > out Implementor ID and Part Number. However, Mellanox doesn't program
> > our own ID yet but we set the Part Number as 0xd08 (A72).
> > According to my folks, ARM's A53, A57, A72, and A73 designs all have
> > 64B CL. If that's true, can I push a patch to make the change?
> 
> Yes. Broadcom Stingray has the same situation i.e Use flags_generic,
> machine_args_generic
> 
This will solve only the native compilation issue. It will not address distro compilation (may be this is not your goal?).

> >
> > Please comment.
> >
> >
> > Thanks,
> > Yongseok
> >

  reply	other threads:[~2019-01-05 22:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-04 19:59 [dpdk-dev] " Yongseok Koh
2019-01-05  5:14 ` [dpdk-dev] [EXT] " Jerin Jacob Kollanukkaran
2019-01-05 22:47   ` Honnappa Nagarahalli [this message]
2019-01-06  7:56     ` Jerin Jacob Kollanukkaran
2019-01-14  7:47       ` Honnappa Nagarahalli
2019-01-14  8:05         ` Jerin Jacob Kollanukkaran
2019-01-16  1:57           ` Honnappa Nagarahalli
2019-01-18  5:50             ` Honnappa Nagarahalli
2019-01-23  9:05               ` Jerin Jacob Kollanukkaran
2019-01-23 16:28                 ` Honnappa Nagarahalli
2019-01-28 12:56                   ` Jerin Jacob Kollanukkaran
2019-01-31 18:09                     ` Honnappa Nagarahalli
2019-02-01 17:16                       ` Jerin Jacob Kollanukkaran

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=AM6PR08MB3672E80CA3555036263E65A5988F0@AM6PR08MB3672.eurprd08.prod.outlook.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=Gavin.Hu@arm.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=mrosenbluth@mellanox.com \
    --cc=nd@arm.com \
    --cc=russell@mellanox.com \
    --cc=yskoh@mellanox.com \
    /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).