From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 453D342FE2; Sat, 5 Aug 2023 23:33:04 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D0895410EE; Sat, 5 Aug 2023 23:33:03 +0200 (CEST) Received: from mail.redfish-solutions.com (mail.redfish-solutions.com [24.116.100.90]) by mails.dpdk.org (Postfix) with ESMTP id 5431540A81 for ; Sat, 5 Aug 2023 23:33:02 +0200 (CEST) Received: from smtpclient.apple (macbook3-8.redfish-solutions.com [192.168.8.12] (may be forged)) (authenticated bits=0) by mail.redfish-solutions.com (8.17.1/8.16.1) with ESMTPSA id 375LWwJu094247 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 5 Aug 2023 15:32:58 -0600 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\)) Subject: Re: Drivers, architectures, processor families, etc. From: Philip Prindeville In-Reply-To: Date: Sat, 5 Aug 2023 15:32:37 -0600 Cc: Stephen Hemminger , dev@dpdk.org Content-Transfer-Encoding: quoted-printable Message-Id: <0C54E384-5177-4075-A935-3528F5FB31B2@redfish-solutions.com> References: <45384262-9744-4975-B5FB-D5D26608DF5B@redfish-solutions.com> <20230802154759.0befb39c@hermes.local> To: Bruce Richardson X-Mailer: Apple Mail (2.3731.600.7) X-Scanned-By: MIMEDefang 3.4.1 on 192.168.8.3 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org > On Aug 3, 2023, at 2:17 AM, Bruce Richardson = wrote: >=20 > On Wed, Aug 02, 2023 at 03:47:59PM -0700, Stephen Hemminger wrote: >> On Wed, 2 Aug 2023 15:49:54 -0600 >> Philip Prindeville wrote: >>=20 >>> Hi, >>>=20 >>> I'm trying to come up with some Kconfig logic for OpenWRT packaging = to help users select the right build options for their hardware. >>>=20 >>> Most OpenWRT developers typically cross-compile, so we obviously = can't rely on detection on the build host as that's rarely the same as = the target machine. >>>=20 >>> Looking in the DPDK repo, I don't see any description of the = available architectures, drivers, etc. and what I had seen previously = was (if I remember) only for x86_64 hardware, and even that I can't seem = to locate again. >>>=20 >>> Would it make sense to put some of these definitions into the repo = itself, so that when new drivers are added, that stands out (at least in = the commit logs) and we can capture the permutations of what driver goes = with which SoC on what architecture, etc? >>>=20 >>> Thanks, >>>=20 >>> -Philip >>>=20 >>=20 >> DPDK now uses meson which by default builds everything available on = the build architecture. >> There is intentionally no way to disable drivers, you can disable = some libraries though. >=20 > Actually, we do now support disabling drivers, and also only = selectively > enabling specific ones. See disable_drivers and enable_drivers meson > options. >=20 > To find our different architecture support, I suggest looking in the = config > directory. The subfolders there often contain cross-files for meson = for > building for various architectures. For example, config/arm, contains = a > number of reference files for cross-compiling for different arm = platforms. >=20 > Regards, > /Bruce 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? -Philip