From: Philip Prindeville <philipp_subx@redfish-solutions.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Subject: Re: Drivers, architectures, processor families, etc.
Date: Tue, 8 Aug 2023 10:38:51 -0600 [thread overview]
Message-ID: <DEFAD7A1-81CA-4FD7-B87A-3AD7B6BE78A4@redfish-solutions.com> (raw)
In-Reply-To: <ZNH6Mvo96lVKF0cd@bricha3-MOBL.ger.corp.intel.com>
> On Aug 8, 2023, at 2:17 AM, Bruce Richardson <bruce.richardson@intel.com> wrote:
>
> On Sat, Aug 05, 2023 at 03:32:37PM -0600, Philip Prindeville wrote:
>>
>> Noticed also that the ARM architecture has configs, but AMD64 seems to be wide open... just one generic config.
>>
>> Is that because some chips, like Xeon-D have on-die NICs, and others like Xeon-E don't?
>>
>
> Its just that folks generally don't cross-compile for x86, and also the
> fact that nobody has ever brought it up before. We have no "native-build"
> files in DPDK, only cross-files for cross-compilation. However, if there is
> demand for them no reason we can't store some.
>
> /Bruce
We bought a Mac Studio (fully configured) for doing in-house CI/CD, and it was beating the pants off of any of our Xeon servers, so now we build everything either on an M2 Mac or on a Graviton EC2 instance.
Native builds are overrated. :-)
-Philip
next prev parent reply other threads:[~2023-08-08 16:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 21:49 Philip Prindeville
2023-08-02 22:47 ` Stephen Hemminger
2023-08-03 8:17 ` Bruce Richardson
2023-08-05 21:32 ` Philip Prindeville
2023-08-08 8:17 ` Bruce Richardson
2023-08-08 16:38 ` Philip Prindeville [this message]
2023-08-03 16:40 ` Philip Prindeville
2023-08-08 8:29 ` Bruce Richardson
2023-08-14 15:31 ` Ferruh Yigit
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=DEFAD7A1-81CA-4FD7-B87A-3AD7B6BE78A4@redfish-solutions.com \
--to=philipp_subx@redfish-solutions.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).