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 ED50EA00C3; Mon, 3 Oct 2022 14:36:03 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B99D440DFB; Mon, 3 Oct 2022 14:36:03 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 1F91A40695 for ; Mon, 3 Oct 2022 14:36:02 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1664800561; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=gl9ivDihLXxzcyZdd2axqhzx81K2ODcuLp7Rw691Nv8=; b=QbblH/5Ii8rbgmvDMe+0FzbR7ckWhQXeb8UgjDkelLFXJHDMmnlvDX8eFfZ1POxmdK6P3I N6OYAqFMfOqTd7cY9Cmn4H4c3ndZXo03ii5Ylvk813S+EvDk5MprA7fFmDJTm2SitVknvN REnX2h/bnJzkZRefPqmjAH9K+TNpGIA= Received: from mail-pg1-f198.google.com (mail-pg1-f198.google.com [209.85.215.198]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-674-x8lNm529P6W8-Hb39mdeTQ-1; Mon, 03 Oct 2022 08:35:58 -0400 X-MC-Unique: x8lNm529P6W8-Hb39mdeTQ-1 Received: by mail-pg1-f198.google.com with SMTP id a33-20020a630b61000000b00429d91cc649so6882086pgl.8 for ; Mon, 03 Oct 2022 05:35:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=gl9ivDihLXxzcyZdd2axqhzx81K2ODcuLp7Rw691Nv8=; b=3aqRH665CjdV+l7D1mmqg3v+lpTYrAGmcPpWSER2asAjGY3G4z9CdACbQPZ1Z8CzxK iHt9R08ixz1B55IWHYGThUeT2P3PBtS83rBBvJykUFuluBC/TOF5nm4aA5KaJA6a2KO+ FPvmChxaFjZT0a4zeQwcRqacSOOcMtrqZ7Jbs10OWUfVKeYFj4FUvQgpG4A80lAxOnr7 Rq26HgESQh4VhM1Bxbd/3hnDmzbyfBHbe4V2LYYqynCrJLWbzuGn0LjAa/636KHyNxvD C67Y4GAO1M8JZUX4pyei50LlVK4MSFaPpNxhYSzIBunnub9kvprzb3kLtXL6cmyk6mPN VmzA== X-Gm-Message-State: ACrzQf1nr/n1baYG5PwZfOUO9P+8z1AVMpBXE1I0OtRw5uGIsyr9+Z7b DNkpmO4hq0sgM7UEWHf629DBdaVzlkml27n6x2v3zAJv0rQ/RmyONGyz9oWYuf0YnBkOGqXXsyJ DU6hb+l1lZMQ2Whaim1s= X-Received: by 2002:a17:90a:428e:b0:205:d5fe:e0b3 with SMTP id p14-20020a17090a428e00b00205d5fee0b3mr11869693pjg.33.1664800557727; Mon, 03 Oct 2022 05:35:57 -0700 (PDT) X-Google-Smtp-Source: AMsMyM5G9cnb6bc7amFeXmnYALKMA0tTRvo8lwHjNviqdHDOwCs6M9PtM/XeaFnXu96qE+wruP5Aw5v6R1FPPYWFq6w= X-Received: by 2002:a17:90a:428e:b0:205:d5fe:e0b3 with SMTP id p14-20020a17090a428e00b00205d5fee0b3mr11869674pjg.33.1664800557407; Mon, 03 Oct 2022 05:35:57 -0700 (PDT) MIME-Version: 1.0 References: <20220419161438.1837860-1-kevin.laatz@intel.com> <20220603143601.230519-1-kevin.laatz@intel.com> <7465552.R56niFO833@thomas> In-Reply-To: From: David Marchand Date: Mon, 3 Oct 2022 14:35:45 +0200 Message-ID: Subject: Re: [PATCH v7] eal: add bus cleanup to eal cleanup To: Bruce Richardson , Kevin Laatz Cc: Thomas Monjalon , dev , =?UTF-8?Q?Morten_Br=C3=B8rup?= , Li Zhang , Matan Azrad , Stephen Hemminger , lihuisong X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" 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 Hello Bruce, Kevin, On Mon, Jun 13, 2022 at 5:59 PM Bruce Richardson wrote: > > > For info, Li has sent a patch for the bus cleanup > > > which is not updating the bus code: > > > https://patches.dpdk.org/project/dpdk/patch/20220606114650.209612-3-lizh@nvidia.com/ > > > It may be a temporary solution before the deprecation. > > > > On the principle, that's probably the best, there is no question about > > unclear frontier of the ABI. > > (In practice though, the mentionned patch is triggering segfaults in > > two CI, for pdump). > > > > Hiding rte_bus object should be straightforward in v22.11, I had some > > patches, but never finished the work. > > > > It would be great too, to look into rte_driver and rte_device which > > are exposed important types, but that's another story. > > > Agreed, we need to look into all this for 22.11 release, let's defer this > patch until we get proper deprecation process. Temporary patch looks fine > as a fix too. The patch needs some rebasing for making it into 22.11. Can you work on it, this week? Thanks! -- David Marchand