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 2CC4D2C52 for ; Tue, 24 Apr 2018 22:05:13 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 6465B212DB; Tue, 24 Apr 2018 16:05:12 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Tue, 24 Apr 2018 16:05:12 -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=qdJqIj1eM4cCyvlu/f/qR+D3sd UogRzPZafrVbePy9Y=; b=bdpYvyIs6S5lI9Pne7vmKXTV/wYcoKHvz7mIUkTpQM rZOb2JChDA7ocwWV+j3tukz9xc6AwahpaCzpLdrTCW/zHZcrh6RYHhUPMKzIKUy3 MyotICYSU4jMWXE90A+dz6UlcmW3K02uCqIEePybpML0iuP+7xjfrFmaFwXX/Gar A= 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=qdJqIj 1eM4cCyvlu/f/qR+D3sdUogRzPZafrVbePy9Y=; b=gdT2MwgFrCKS7bYUJQ4oZE u9HEd3Z+hrlDJ88kBIGX4goYplf7+tBfLi0F8rLrGiq/MWHeFUW/pmjqv++TmyZL Rc47F+L0cEnAecYpw/1JmrVsVEoOeq34OEBKCJK7jtdNyevshEEBgDUVh/8hXk1q iYnUhlWQrx5IZxcrL6+bZYm05Tp4U3ecouEvxvyN+l1gCyaKoLhvxgIrRe+rYqhy g/17cfjSXicGuHQZsGP3TiBtOsgxsqmCi7uXW868MJWZ0GdFSOmjQlETYoywbKch 5g/WS0Yx27HlJbzfjmRDkMos6f4HTjPq3GpgnCYfQ1Ob2wanEDgKDDhG00nacLoQ == 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 9911EE4488; Tue, 24 Apr 2018 16:05:11 -0400 (EDT) From: Thomas Monjalon To: "Burakov, Anatoly" Cc: Stephen Hemminger , dev@dpdk.org, bruce.richardson@intel.com Date: Tue, 24 Apr 2018 22:05:10 +0200 Message-ID: <2542114.cvfhNbjQKQ@xps> In-Reply-To: <3898cc9f-f41f-de8e-a89f-f8f35c7444e8@intel.com> References: <20180424093242.6c35534b@xeon-e3> <3898cc9f-f41f-de8e-a89f-f8f35c7444e8@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2 0/2] Fix file locking in EAL memory 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 20:05:14 -0000 24/04/2018 19:25, Burakov, Anatoly: > On 24-Apr-18 5:32 PM, Stephen Hemminger wrote: > > On Tue, 24 Apr 2018 16:54:21 +0100 > > Anatoly Burakov wrote: > > > >> One of the ways to work around this was using OFD locks, > >> but they are only supported on kernels 3.15+, > > > > Maybe time to move to next LTS kernel (3.16)? > > > > I'm all for it, but it's not my call to make :( I am in favor of upgrading kernel requirements. The discussion already started few months ago: https://dpdk.org/patch/34778 We just need to consider how to support the latest versions of distributions Debian, Ubuntu, SLES and RHEL.