From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw0-f178.google.com (mail-yw0-f178.google.com [209.85.161.178]) by dpdk.org (Postfix) with ESMTP id EE8E62716 for ; Mon, 19 Sep 2016 15:52:55 +0200 (CEST) Received: by mail-yw0-f178.google.com with SMTP id t67so145264851ywg.3 for ; Mon, 19 Sep 2016 06:52:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Tb2c9e8WfMFe+fdE52RkMIIyZ+WvehgNtSsBS1PXuxE=; b=fCAl7eSHTQ+YB8xdXK8b5cW+ReOUg7UOU7b0jnBqSqwN/qfSmkqwcqqX122oQfLWu3 FGCI1oJfOG1GjZWSY/YC6ZVAGiAyJ+AlYQjigjcODd8tEAI8TQDxFvmw6MES4etZm5ZY qbXw33tK8fDsCTMQ3aKi94IA1HQZR84uKTm1jh62vaM2OngZ+Z2Zvqh4c+k0tmS/xIRb NYn4Wk4Fy34/kzSI8fLRUWQ3dvqt7EKi3HV0K991Fx97G1pREoxy0wHYf3ESCBTnaoB/ erbRDQbQP9Oz6GRPv89rK8+6Z79jmG15nzVbRf3ZNVgC6IzQl+NHks+iEVP7M543fRb5 tBow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Tb2c9e8WfMFe+fdE52RkMIIyZ+WvehgNtSsBS1PXuxE=; b=J2k8GrloWinW3stBaExIaa2kpJdTkkHiw/BtB1dUwq8S/ADLtRbodDMXR6P6lkpaLW lAXQwz5cwLTCDQtPLNYbg7OFrfmASQ/RPijfZ4b11CGnZZZw+w485e0C+vuSMZwO39GV HByHKU0PAcx1SfoUnUy9qvRlusJ674M1E2eucUjocXzDIWdgDpR6LEiEppq2AnxCyLlz T9XHKlY6BdsR1o/HCyIug9OMlfoef4PgFDFU7oiWNK186VZiAsVGc2V0hNFebAl3/PEs yQd6598weiggMggcz6eGuusvM0dg8m5L7m1kVZ+qg/ACLLSgaMmyMNNYS7PnP9zNgpTq qrxQ== X-Gm-Message-State: AE9vXwMUZ3gqmbcagkp+bxaQfVMCXm1mUCje4jqrYK2upu2jULz4bSs8C8BR/Ns17tJrlvuFXJgoQ92njvOxsqSl X-Received: by 10.129.95.70 with SMTP id t67mr27085689ywb.284.1474293175428; Mon, 19 Sep 2016 06:52:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.13.243.194 with HTTP; Mon, 19 Sep 2016 06:52:25 -0700 (PDT) In-Reply-To: <20160919132932.GA45256@bricha3-MOBL3> References: <1472489448-15911-1-git-send-email-yury.kylulin@intel.com> <20160919132932.GA45256@bricha3-MOBL3> From: Christian Ehrhardt Date: Mon, 19 Sep 2016 15:52:25 +0200 Message-ID: To: Bruce Richardson , stable@dpdk.org Cc: Yury Kylulin , helin.zhang@intel.com, "Ananyev, Konstantin" , jingjing.wu@intel.com, wenzhuo.lu@intel.com, dev Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] [PATCH 0/2] fix mbufs leakage during Rx queue release on ixgbe/i40e X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2016 13:52:56 -0000 On Mon, Sep 19, 2016 at 3:29 PM, Bruce Richardson < bruce.richardson@intel.com> wrote: > > This patch set fixes problem when mbufs are not released back to the > > original memory pool during Rx queue relese call leading to mbufs > > "leakage". > > > > This issue happens when device stop (rte_eth_dev_stop()) will be called > > after device start (rte_eth_dev_start()) without any incoming packets > > received since device start. In this case both rxq->rx_tail and > > rxq->rxrearm_start equal to 0 and release cycle will not be executed. > > On the next device start (rte_eth_dev_start()) new set of mbufs for the > > RX queue will be allocated. > > > > Yury Kylulin (2): > > net/ixgbe: fix mbufs leakage during Rx queue release > > net/i40e: fix mbufs leakage during Rx queue release > > > Applied to dpdk-next-net/rel_16_11 > I don't know the underlying code well enough, but given the description I'd expect that qualifies for the stable tree? Set stable@dpdk on cc.