From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 2A42C4C99 for ; Wed, 25 Apr 2018 01:00:26 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 7EBE720EDC; Tue, 24 Apr 2018 19:00:25 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 24 Apr 2018 19:00:25 -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=R48fd2r9fICV3eoMScn+G6b9Mg VriXIbfQk9C1WTObA=; b=gf1f2U8iaZSDg2QRhHW0O6oCKkw3qZ3U2MZc2vtjq3 V0nkWGsCSZbN/tScB05MPCNwYWqJ9jmOX8XC4kIjb3EPk7zNderO8eJ54FqfBaiy dYxoD5Qr2u7qVpjK50wx7tTxqudrRlnxfFkYtaPxdRvAviuTPaXcj1UCu7KjxQ1B M= 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=fm2; bh=R48fd2 r9fICV3eoMScn+G6b9MgVriXIbfQk9C1WTObA=; b=nsgyhxONMXv5Z01QS1jLuo TopkvBM2JB7QB4ZyqHxi64A5xIP1LhCkVA2PdtQwF8gWb7mSlVilnEEJ+v0WSMsO 9wqgMI4F5QqjStNDZw5SNY+I7gEP1BvFFTNsxJNT1nUAHeCUli0jZVzP6nZcqPrr w9Tiq9PQPJnSNABc0rVSrQoyJU3WQNEEltYCCU2fb9699Gjv2AVm16sSol1D13Qz FBY1UY+kwBe3NPp3z2CJDpJhUebQjkEEV4gjxR5C8HveCmob9jD5IlvLgdLSpk7T SN9plEErzYRmr3f9cEZ2wopaJTbB3JJxg9p/8k7qrKZLrzIYl4JUMr5of31rkuoQ == 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 DD1C2E4ED0; Tue, 24 Apr 2018 19:00:24 -0400 (EDT) From: Thomas Monjalon To: Olivier MATZ Cc: dev@dpdk.org, Andrew Rybchenko Date: Wed, 25 Apr 2018 01:00:23 +0200 Message-ID: <3270124.pgnYCBJxfz@xps> In-Reply-To: <1523885610-20014-1-git-send-email-arybchenko@solarflare.com> References: <1511539591-20966-1-git-send-email-arybchenko@solarflare.com> <1523885610-20014-1-git-send-email-arybchenko@solarflare.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2 0/6] mempool: add bucket driver 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, 24 Apr 2018 23:00:26 -0000 Can we have this patchset in 18.05-rc1? Or is it candidate to rc2? 16/04/2018 15:33, Andrew Rybchenko: > The patch series adds bucket mempool driver which allows to allocate > (both physically and virtually) contiguous blocks of objects and adds > mempool API to do it. It is still capable to provide separate objects, > but it is definitely more heavy-weight than ring/stack drivers. > The driver will be used by the future Solarflare driver enhancements > which allow to utilize physical contiguous blocks in the NIC firmware. > > The target usecase is dequeue in blocks and enqueue separate objects > back (which are collected in buckets to be dequeued). So, the memory > pool with bucket driver is created by an application and provided to > networking PMD receive queue. The choice of bucket driver is done using > rte_eth_dev_pool_ops_supported(). A PMD that relies upon contiguous > block allocation should report the bucket driver as the only supported > and preferred one. [...] > Andrew Rybchenko (1): > doc: advertise bucket mempool driver > > Artem V. Andreev (5): > mempool/bucket: implement bucket mempool manager > mempool: implement abstract mempool info API > mempool: support block dequeue operation > mempool/bucket: implement block dequeue operation > mempool/bucket: do not allow one lcore to grab all buckets