From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id AECB7A48F for ; Mon, 15 Jan 2018 16:29:55 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Jan 2018 07:29:54 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,364,1511856000"; d="scan'208";a="195696886" Received: from jguo15x-mobl3.ccr.corp.intel.com (HELO [10.255.24.67]) ([10.255.24.67]) by fmsmga006.fm.intel.com with ESMTP; 15 Jan 2018 07:29:52 -0800 To: Thomas Monjalon References: <1515575544-2141-3-git-send-email-jia.guo@intel.com> <6774704.u5U2Uf1Nb3@xps> <3468196.BpI31Qveuv@xps> Cc: dev@dpdk.org, stephen@networkplumber.org, bruce.richardson@intel.com, ferruh.yigit@intel.com, gaetan.rivet@6wind.com, konstantin.ananyev@intel.com, jblunck@infradead.org, shreyansh.jain@nxp.com, jingjing.wu@intel.com, helin.zhang@intel.com, motih@mellanox.com From: "Guo, Jia" Message-ID: Date: Mon, 15 Jan 2018 23:29:52 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <3468196.BpI31Qveuv@xps> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH V10 1/2] eal: add uevent monitor api and callback func X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jan 2018 15:29:56 -0000 On 1/15/2018 7:32 PM, Thomas Monjalon wrote: > 15/01/2018 11:55, Guo, Jia: >> On 1/15/2018 7:16 AM, Thomas Monjalon wrote: >>> Hi, >>> >>> 11/01/2018 15:05, Jeff Guo: >>>> +/* A genaral callback for all registerd devices */ >>> Typos: genaral, registerd >>> >>> So the callback is only for registered devices? >>> What about hotplugged devices? >> the hotplugged devices is managed by the application, if it prior >> registered and in the app's hotplug device list, will always be monitor >> whenever it plug in and out. the eal only care about the registered >> devices. > I disagree. The application needs the EAL service to get notified > of a new device plugged in. > We should find a way to register the callback for all devices, > including new ones. i think the current mechanism would let eal service detect all new device in , but would not notify all to the application. if the application need to monitor specific device , it will prior know the device name. but if notify all in eal service and let application choose it in user side ,that is other story, that is what you want ? but do you think about , if it is need to let user know all device plugin , or just let eal know all info would be better or safer?