From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f174.google.com (mail-wr0-f174.google.com [209.85.128.174]) by dpdk.org (Postfix) with ESMTP id 1515968C1 for ; Wed, 10 May 2017 00:10:39 +0200 (CEST) Received: by mail-wr0-f174.google.com with SMTP id z52so18499428wrc.2 for ; Tue, 09 May 2017 15:10:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=sbKQc2G0OatvogDup7+n3wp6HKTMza63PZJ0kLpnNvg=; b=0AwZlsI6QY+kUrgS1yV+NM/3RDY+iKRrInK3K1VoOur3SkTUDipuPS9MFlzQ50Lldb 7h6o0FGgx13FzcvvIsQjPRLizM2f8DfRvjV/39+a7VWiJPL7r5BRmPSCWQ6CrMWeDTQo 7wrrhkbBAq769FQFBeF8qUjRruomc8k1axVWOFC8Qwmgaojytob2X29CszN3+icbzWcL f4afofM0Dnw0sAl5o0JeyGCa9G/Kblhcgkb0atpwUeLlIUjKpF9OSytOJFYZCvbSdRDz FE81QTwaNXAjCBW1pLlxOvVNBI46NsA+ygUBN3u5JtpSFFieRTkmpiRg5FVT50gPcrRI T9tg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=sbKQc2G0OatvogDup7+n3wp6HKTMza63PZJ0kLpnNvg=; b=Yv2TydbE+vkN13SM2E9eEALjRRoHR3WDglMAyMgHRIaI4dPYiaxb6bpISM+QMCCEAj 9mz/Q/+PochnmTuJXkoxffyiW49hxxJ5RwFCQj04uNt+pQorSGWYwNtpZjY6Vasw6lGP IoTvGFRss4fGylyXqEKbB3pG3dpFdPcdBhEbgkS9YDRngeJSt1cYGajsJbj9yX40ihNH DL/RyZByNbmXSj6XOr7RPEmEBEp44EUF8VykIFuNrEN7I1Ln2JzZW1erY349w1o9v3V0 lBzd00eJEB3f3wqxG6XHVeHwwMDz05p5duXMPyKpHID3pLyXMkTl8aceSMiVCy1HRQWT 9T1w== X-Gm-Message-State: AODbwcCdHKNAzU5tx5FRGm4K0OM4HLz41HAndFOmXo6fub4BvDKRPzKA 136SCC6uFyrXAd4l X-Received: by 10.223.169.34 with SMTP id u31mr1592874wrc.46.1494367839783; Tue, 09 May 2017 15:10:39 -0700 (PDT) Received: from 6wind.com (host.78.145.23.62.rev.coltfrance.com. [62.23.145.78]) by smtp.gmail.com with ESMTPSA id g137sm2458868wme.27.2017.05.09.15.10.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 May 2017 15:10:38 -0700 (PDT) Date: Wed, 10 May 2017 00:10:33 +0200 From: Adrien Mazarguil To: Yongseok Koh , Thomas Monjalon , Ferruh Yigit Cc: dev@dpdk.org, nelio.laranjeiro@6wind.com, hhaim@cisco.com Message-ID: <20170509221033.GQ16218@6wind.com> References: <20170506012018.18579-1-yskoh@mellanox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [dpdk-dev] [PATCH v2 0/2] net/mlx5: fix erroneous index handling for Tx ring 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, 09 May 2017 22:10:40 -0000 On Tue, May 09, 2017 at 01:49:29PM -0700, Yongseok Koh wrote: > This patchset is to fix a critical bug which can occur in case of resource > deficiency on Tx path. Flowing multi-segment packets can accelerate the > occurrence rate. > > v2: > * Split the patch into two separate ones to make back-port easier. > * Added "Fiexes:" tag and "CC: stable@dpdk.org" for the bug fix. > > Yongseok Koh (2): > net/mlx5: fix erroneous index handling for Tx ring > net/mlx5: change error-prone code on Tx path > > drivers/net/mlx5/mlx5_rxtx.c | 51 +++++++++++++++++++------------------------- > 1 file changed, 22 insertions(+), 29 deletions(-) For the series: Acked-by: Adrien Mazarguil Thanks for extracting the fix into a separate patch. Ferruh, Thomas, is there still time to include this for 17.05 given the seriousness of this bug? -- Adrien Mazarguil 6WIND