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 BC8C7A0540; Thu, 7 Jul 2022 11:29:59 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 60F9E40A7B; Thu, 7 Jul 2022 11:29:59 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 1BF98406B4 for ; Thu, 7 Jul 2022 11:29:57 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1657186197; 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=qUNEUzw9MWR8wwSp73Rg7m64a6B3MeChyoq93H/cFaM=; b=XlUFvGP/hVZK34tdXll/ymOQ3gK66w6ah9bualb8zPou76ouTuyi7598ar7jlfhSiAlXe7 3wd7kuLrFG+AEH8COoivgXl5mpEVMTEnLwy/aD3tBUwI0KWe6/NJy4QAonJ4DP0DsRLJ+N ua1P+hcP9sRXmq0+GvKoH+LAJPUbOZw= Received: from mail-lf1-f71.google.com (mail-lf1-f71.google.com [209.85.167.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-331-xaJLZK1gNlK9UlDSU49Q7Q-1; Thu, 07 Jul 2022 05:29:54 -0400 X-MC-Unique: xaJLZK1gNlK9UlDSU49Q7Q-1 Received: by mail-lf1-f71.google.com with SMTP id i3-20020a056512318300b0047f86b47910so6158074lfe.14 for ; Thu, 07 Jul 2022 02:29:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qUNEUzw9MWR8wwSp73Rg7m64a6B3MeChyoq93H/cFaM=; b=sQtKlY9ebFStdSjVMVJJl+JTBaHCPlU78hd18vTYa9eLoofyJAfKrOguSG+5NrjZfn /Y4cw1jzJiJMKmiLIIltDfBzdQ6gug1ZYA+FVb/PFj7KvIRGQorcPq5cuTCnwaC4YyGu /0ZJQO7WnrNG1TWLhCgJX0GYD+Bi14+ZtRThf9o5RgFYjVdZXU6glGJUNTTLFfNNBfNG AajGI6X8Z7X2+mVLRCUPU+L3HIJEfOkmwnETncl5KiEb1OKG2qWPpZ5Fs7u9rZZQcO2Y m+3WygKeK5YwN5j5kqETQFQmzWODlE22S00RvNDpFYJaxLfU/Z4pEzrCaF0MkuFIDZXh dkfw== X-Gm-Message-State: AJIora+DTpQCQ4ueh5VsMKnTPr0vHG3AmU+iO0lliiTwWXJCTR/UHijF TFfOGC9HxD1P4zoVwKWR6blX6x0JEUOOXbU6vN+10VGnS+UK45cjjA417vonCkZlKQmwBG78ZMR jy1BS1U19RcH3LYnqetM= X-Received: by 2002:a05:651c:38e:b0:25a:7182:410d with SMTP id e14-20020a05651c038e00b0025a7182410dmr26423021ljp.81.1657186192519; Thu, 07 Jul 2022 02:29:52 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tFKK1Hb+EOFVPtq8KItsPpCgsccxAXoyU22bMv6pLmTlJ2veROpha4B9ZRug0V7HvBw/n3/652jjW8eBR9xYY= X-Received: by 2002:a05:651c:38e:b0:25a:7182:410d with SMTP id e14-20020a05651c038e00b0025a7182410dmr26423010ljp.81.1657186192326; Thu, 07 Jul 2022 02:29:52 -0700 (PDT) MIME-Version: 1.0 References: <20220630094129.2066164-1-david.marchand@redhat.com> In-Reply-To: From: David Marchand Date: Thu, 7 Jul 2022 11:29:41 +0200 Message-ID: Subject: Re: [PATCH] doc: announce some raw/ifpga API removal To: "Huang, Wei" , "Zhang, Tianfei" , "Xu, Rosen" Cc: "dev@dpdk.org" , Ray Kinsella Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dmarchan@redhat.com 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 On Fri, Jul 1, 2022 at 10:35 AM David Marchand wrote: > > > > > > Can't this application use rte_dev_remove and rte_dev_probe? > > > > > > If not, we should add the missing parts in the API. > > > > > > > > > > > Both rte_dev_remove and rte_dev_probe need rte_device pointer. In > > > > > this application, it only know the device's PCI address, is there an existing API > > > to get the rte_pci_device pointer by its PCI address ? > > > > > > > > rte_dev_probe takes a devargs string as input. > > > > int rte_dev_probe(const char *devargs); > > > > > > > > You need the rte_device for removing which can be retrieved from > > > > rte_rawdev_info_get. > > > > > > Additionnaly, rte_eal_hotplug_{add,remove} do the same jobs, but with an > > > easier(?) interface. > > > > > > > > I checked rte_eal_hotplug_{add,remove}, they should meet my requirements, thanks a lot. > > Cool, thanks. So it seems there is nothing blocking for this API change. Could you ack the deprecation notice? Thanks. -- David Marchand