From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 505B71BE40 for ; Tue, 3 Jul 2018 11:27:40 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id AEA8821D23; Tue, 3 Jul 2018 05:27:39 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 03 Jul 2018 05:27:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=C8KCHy2ezJwZnJISwtdDO0DXWZ KzbvW0VPdF9dYLA/E=; b=iyhw4tcKhcqIyO+yxqs99y30hz5HM+g7wOnUZ1rTND fD5tb+DjUjabu3ExZfQZ1pU79BN9jR1ibz87ErUUc3oZTfYYwV67VfL0gk1X9v0f A9MnykHj87NdsTDvACm0TvPkQC9ffFQsutHacC175igXyBUxhy9H7Gj6bnIKy+bC k= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=C8KCHy 2ezJwZnJISwtdDO0DXWZKzbvW0VPdF9dYLA/E=; b=k7Kh8ZHw3aD257WxUGmoBJ cN4eHZEjcpI8/31M/kvu5y5sTH+iOUsx6tJ95j6SoGYXn45Az3BDjYeEgyjDQCJf 03XpxKBpisTVY+GAPdyPAyZKZykLrRlQPPiSdN00A2QkVOckTsySabmMsDQAgk+c xn9TcI4RKsP3K1Tz+jLtu/fdP4g603MGO25KGM3M+biqcV8OJ++LcUnLe8peytP4 bnBQbZ/aXAUBdB5qO3LjvbvlOUseoqeJ5Maflpmc0YPVQVxyBybC7TlQGgRBXfLY 8OuIUGsUsqKu/aax7SKfTit3duLRxJx88yeVKy75XnZggD+4zFwonLaokMGBMjaQ == X-ME-Proxy: X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 28C5E1026A; Tue, 3 Jul 2018 05:27:38 -0400 (EDT) From: Thomas Monjalon To: Qi Zhang Cc: dev@dpdk.org, anatoly.burakov@intel.com, konstantin.ananyev@intel.com, bruce.richardson@intel.com, ferruh.yigit@intel.com, benjamin.h.shelton@intel.com, narender.vangati@intel.com Date: Tue, 03 Jul 2018 11:27:36 +0200 Message-ID: <3358274.MJj7BZBBQ7@xps> In-Reply-To: <20180702054450.29269-3-qi.z.zhang@intel.com> References: <20180607123849.14439-1-qi.z.zhang@intel.com> <20180702054450.29269-1-qi.z.zhang@intel.com> <20180702054450.29269-3-qi.z.zhang@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v8 02/19] eal: enable multi process init callback 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: Tue, 03 Jul 2018 09:27:40 -0000 Hi Qi, Sorry I do not understand neither the commit log, nor the doxygen. If it can help, consider your reader is in a bad mood and needs a pleasant description. 02/07/2018 07:44, Qi Zhang: > Introduce new API rte_eal_register_mp_init that help to register > a callback function which will be invoked right after multi-process > channel be established (rte_mp_channel_init). Typically the API > will be used by other module that want it's mp channel action callbacks > can be registered during rte_eal_init automatically. [...] > +/** > + * @warning > + * @b EXPERIMENTAL: this API may change without prior notice > + * > + * Register a callback function that will be invoked right after > + * multi-process channel be established (rte_mp_channel_init). Typically > + * the function is used by other module that want it's mp channel > + * action callbacks can be registered during rte_eal_init automatically. > + * > + * @note > + * This function only take effect when be called before rte_eal_init, > + * and all registered callback will be clear during rte_eal_cleanup. > + * > + * @param callback > + * function be called at that moment. > + * > + * @return > + * - 0 on success. > + * - (<0) on failure. > + */ > +int __rte_experimental > +rte_eal_register_mp_init(rte_eal_mp_init_callback_t callback); It looks the prefix of this function should be rte_mp_