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 B022945BA3; Tue, 22 Oct 2024 19:07:01 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9F1CC40298; Tue, 22 Oct 2024 19:07:01 +0200 (CEST) Received: from mail-qt1-f176.google.com (mail-qt1-f176.google.com [209.85.160.176]) by mails.dpdk.org (Postfix) with ESMTP id 27D6140272 for ; Tue, 22 Oct 2024 19:07:00 +0200 (CEST) Received: by mail-qt1-f176.google.com with SMTP id d75a77b69052e-4603d3e4552so47356361cf.1 for ; Tue, 22 Oct 2024 10:07:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729616819; x=1730221619; darn=dpdk.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=GjZ8Qdb20cEKsV78LBVyGfAxUD+wIxA4JLxTFpDOh+w=; b=FC+AcJ1bpRd1obH9L4x8zgDS2zvfyXbr20mRWvfJt8iMs0Jcsoc2M8iGCa76eGzc7A hP/EWLsAYUDWPSr0LlPQ/ckEV0TVP5KQz+M40Cyl58NwdhtmmGAJUKtNiIpg0vcXWnXg aaJ/628VuT/J/b2kKXmks0YcIKUydqkzPEBA5qbGPLXdUSpFD5ECiS1JPZkldgbq6bsH OwpoG4fpezGOusxvLVESTEWNNkXE79tUK47GGR7SB0I7pkaYlNMVCyyYC9fuWXxD0u2W zutCQOshCzpWmBdXmFyVdFJDuqoijAECRkNOdZhNYLtlox3AVBz2+/9y5t5Zh6FSCSPN ASJQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729616819; x=1730221619; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=GjZ8Qdb20cEKsV78LBVyGfAxUD+wIxA4JLxTFpDOh+w=; b=kMBQkrkE72E009bi2WH4iNchL1o8gGVHYx6QyZ+2hVwiC9PNcMmEaPTceYegclV2If TG0Zqb1qOEKXZU/XPhi3cnuyIWQs8nJaVfVi2sJSYomqGTJRvP/J/jzF3fjGpzR2wuce +Sne1EZ0CW1HmVYCMOFI0mLHdjXzFQrkBxXVb23AMcvg6GP39eM7rrdugcgE6JMQ+yRB Ti1p/skkww+V7N0lUZI0jubSOuXMANqEGRvggoCKdhe3hVcsr712858ATB1kzC9uh3rN 8hVNmxirPgkShV3bKW9jeNF+2SmEsEmwEeDylw1LqeCyYCZFrTgJPvtv9DcUCIYkiJYo Rryw== X-Forwarded-Encrypted: i=1; AJvYcCVC1OBJ+Au5YCkbOdHknx5S+3oPIVUEgJtDYivfSwKmPN1sJBb5SdJf9aouU3TaBTf9dk8=@dpdk.org X-Gm-Message-State: AOJu0YypHkLienXY8VhkSywbVsfpnIs19GD70UOZyAvGkL5YS2bhlW0H oNxNPsRHZV7W6AjmZnB+OxyahFXeFhnlmctlehpAZva22CUn83JABYXpGbSDZyJJNAk8KqwSJXP jRCFqrWcypvIrbP9T2X3DLEIUwr0= X-Google-Smtp-Source: AGHT+IFI63MQMrIzav+vx+Sdo55gO6UwaR7lq5RvfTo2FOYjSl6hWb+OoqEo2KGCSk7LsM3Eq//RvxZGedy6e3nWTj0= X-Received: by 2002:ac8:7f87:0:b0:45b:f451:ad25 with SMTP id d75a77b69052e-46113091c28mr2731261cf.48.1729616819424; Tue, 22 Oct 2024 10:06:59 -0700 (PDT) MIME-Version: 1.0 References: <20241008105415.1026962-1-gakhil@marvell.com> <20241008184915.1356089-1-gakhil@marvell.com> <20241008184915.1356089-4-gakhil@marvell.com> <86546386.BzKH3j3Lxt@thomas> <20241022083057.184690ef@hermes.local> In-Reply-To: <20241022083057.184690ef@hermes.local> From: Jerin Jacob Date: Tue, 22 Oct 2024 22:36:33 +0530 Message-ID: Subject: Re: [EXTERNAL] Re: [PATCH v3 3/9] raw/cnxk_rvu_lf: add PMD API to get BAR addresses To: Stephen Hemminger Cc: David Marchand , Akhil Goyal , Thomas Monjalon , "dev@dpdk.org" , Jerin Jacob , Harman Kalra , Bruce Richardson , Hemant Agrawal , Sachin Saxena , Ferruh Yigit Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 Tue, Oct 22, 2024 at 9:00=E2=80=AFPM Stephen Hemminger wrote: > > On Tue, 22 Oct 2024 12:08:22 +0200 > David Marchand wrote: > > > On Tue, Oct 22, 2024 at 8:06=E2=80=AFAM Akhil Goyal wrote: > > > > The rational to NOT pull "Hardware abstraction library using the BA= R > > > > address" to DPDK are > > > > -Yet another 200K of driver C++ code which does not make sense to k= eep > > > > in dpdk.org > > > > -It can not implemenent any of the current subsystems > > > > > > > > In this context, let me know what you think? > > > > This hardware abstraction library will have to call some driver > > specific API (like the added raw/cnxk_rvu API). > > Can this library directly use the PCI driver API, and call the cnxk > > common driver? > > If so, there is no need to add another driver API (that breaks > > layers), and the rawdev driver is only about adding the mailbox > > features. > > > > > This seems related to the discussion of binary drivers in the TB. > There was discussion that any/all use of binary drivers means that the an= y > crashes in DPDK could be cause by that binary. Like the Linux kernel, > we need a "tainted" policy. Where any bug reports on tainted use of DPDK > are just rejected and forwarded to the binary driver vendor. It is not a binary driver situation, it is more out of tree driver situation i.e DPDK does not depend on any binary drivers. It is the same as exposing rte_pci_device via enable_driver_sdk meson option.