From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <stephen@networkplumber.org> Received: from mail-pg1-f195.google.com (mail-pg1-f195.google.com [209.85.215.195]) by dpdk.org (Postfix) with ESMTP id 9138E4CC7 for <dev@dpdk.org>; Fri, 10 May 2019 16:59:03 +0200 (CEST) Received: by mail-pg1-f195.google.com with SMTP id e6so3153883pgc.4 for <dev@dpdk.org>; Fri, 10 May 2019 07:59:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=ee5xvWaZDrAyG+8fmGolRj/BNbMrmf2TyKwgxz2kL4w=; b=nuxZGQPXqASGr/+gcbYHZ+UfewscUsEJ+K1dZpi/YUAS5/Xcob4RljlMJ6lE4YYLrF TnnduBhhwMEpdQGc0FzLYM5fAMce1SJLBKm60M31bWFxdEN1d9ubrWQvBpF7qlj5xnpU pAmlVw91X2+tofTsd/k6XJ0cT8ZiIU4tmrn+LGyVCxSTZ24+obwXqAQtGausaI6Xv394 chQnM7m1I3Hocc25iYWJnZrDXsbZUnKsshHmlgr63xtEZHLzIlPozZMOjrU0tdp72x+x BeS7ib9lTpH5geMBWUGrMxSWe6vvvYrsLWGjglPLPgHUhIAq1rJb1eC6Z7KPTYimQRa+ kX9w== 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:in-reply-to :references:mime-version:content-transfer-encoding; bh=ee5xvWaZDrAyG+8fmGolRj/BNbMrmf2TyKwgxz2kL4w=; b=tapMOeto2KyCADXfa7jfyfAxrJdmWJr4BiiTnzijfutT5qV5wFeXMklUMOKtK7O8iP SjX+t6HS07pasHC3ZUKQbfpQ9AVRYsmd2gDn7wNJ0Ee1lIYNLeDDtOdzbQ6vhwCCmdYk QB7K5tlF9iBu8xpqvtIYL4kMPefqq+hX6edDzU0hS7906Bq2W8PQn1GzuqrXz3ol03du zpdOgFpFPUEhNJMbH991yYhzv/L1PkYcUs4yWE7DHHYu5ADGQb/2JhF/AbBE9u8EuhKT pPuu/mtyRxqs6gK0Aa6y0yULKrE/cTks+jno6e4oLJmfka3NEnbTE06LWphHOgVpsFj2 CyNg== X-Gm-Message-State: APjAAAXFVC7qTi5NTKnvE85DVDqGkhSnANoLNuWkO8m1I4GTtNzelKQr 2l4X7brWjQoAs68N+M/3mSeJPA== X-Google-Smtp-Source: APXvYqyNH4NYlDZcwbKIll05NR0WQTDgL47PpyR1MTUIPuI9tyAq8g/V8htHZ+Rmx9uzE8KFyLzzEg== X-Received: by 2002:a62:6c88:: with SMTP id h130mr14703771pfc.106.1557500342697; Fri, 10 May 2019 07:59:02 -0700 (PDT) Received: from hermes.lan (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id s17sm7013125pfm.149.2019.05.10.07.59.02 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 10 May 2019 07:59:02 -0700 (PDT) Date: Fri, 10 May 2019 07:58:55 -0700 From: Stephen Hemminger <stephen@networkplumber.org> To: "Eads, Gage" <gage.eads@intel.com> Cc: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>, "olivier.matz@6wind.com" <olivier.matz@6wind.com>, "arybchenko@solarflare.com" <arybchenko@solarflare.com>, "Richardson, Bruce" <bruce.richardson@intel.com>, "Ananyev, Konstantin" <konstantin.ananyev@intel.com>, "Honnappa.Nagarahalli@arm.com" <Honnappa.Nagarahalli@arm.com>, "gavin.hu@arm.com" <gavin.hu@arm.com>, "Ola.Liljedahl@arm.com" <Ola.Liljedahl@arm.com>, "nd@arm.com" <nd@arm.com> Message-ID: <20190510075855.2899716e@hermes.lan> In-Reply-To: <9184057F7FC11744A2107296B6B8EB1E68CB470E@fmsmsx101.amr.corp.intel.com> References: <20190118153117.23810-1-gage.eads@intel.com> <20190201143623.31135-1-gage.eads@intel.com> <1845234.OyIqJ6yfKh@xps> <9184057F7FC11744A2107296B6B8EB1E68CB470E@fmsmsx101.amr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v4] doc: announce ring API change X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Fri, 10 May 2019 14:59:03 -0000 On Fri, 10 May 2019 14:53:56 +0000 "Eads, Gage" <gage.eads@intel.com> wrote: > > 01/02/2019 15:36, Gage Eads: > > > In order to support the non-blocking ring[1], an API change > > > (additional argument to rte_ring_get_memsize()) is required in > > > librte_ring. This commit updates the deprecation notice to pave the > > > way for its inclusion in 19.08. > > > > > > [1] http://mails.dpdk.org/archives/dev/2019-January/124162.html > > > > > > Signed-off-by: Gage Eads <gage.eads@intel.com> > > > > There is still no agreement on this change? > > > > Still none. I was hoping this discussion (http://mails.dpdk.org/archives/dev/2019-April/129229.html) would lead to some clear direction, but at this point the effort is stalled. The fundamental tradeoff is between non-blocking rings and ABI breakage. Why not have a new ring type for non-blocking rings since non-blocking rings are not necessary for all use cases. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 5EB43A0096 for <public@inbox.dpdk.org>; Fri, 10 May 2019 16:59:06 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 7F37858F6; Fri, 10 May 2019 16:59:05 +0200 (CEST) Received: from mail-pg1-f195.google.com (mail-pg1-f195.google.com [209.85.215.195]) by dpdk.org (Postfix) with ESMTP id 9138E4CC7 for <dev@dpdk.org>; Fri, 10 May 2019 16:59:03 +0200 (CEST) Received: by mail-pg1-f195.google.com with SMTP id e6so3153883pgc.4 for <dev@dpdk.org>; Fri, 10 May 2019 07:59:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=ee5xvWaZDrAyG+8fmGolRj/BNbMrmf2TyKwgxz2kL4w=; b=nuxZGQPXqASGr/+gcbYHZ+UfewscUsEJ+K1dZpi/YUAS5/Xcob4RljlMJ6lE4YYLrF TnnduBhhwMEpdQGc0FzLYM5fAMce1SJLBKm60M31bWFxdEN1d9ubrWQvBpF7qlj5xnpU pAmlVw91X2+tofTsd/k6XJ0cT8ZiIU4tmrn+LGyVCxSTZ24+obwXqAQtGausaI6Xv394 chQnM7m1I3Hocc25iYWJnZrDXsbZUnKsshHmlgr63xtEZHLzIlPozZMOjrU0tdp72x+x BeS7ib9lTpH5geMBWUGrMxSWe6vvvYrsLWGjglPLPgHUhIAq1rJb1eC6Z7KPTYimQRa+ kX9w== 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:in-reply-to :references:mime-version:content-transfer-encoding; bh=ee5xvWaZDrAyG+8fmGolRj/BNbMrmf2TyKwgxz2kL4w=; b=tapMOeto2KyCADXfa7jfyfAxrJdmWJr4BiiTnzijfutT5qV5wFeXMklUMOKtK7O8iP SjX+t6HS07pasHC3ZUKQbfpQ9AVRYsmd2gDn7wNJ0Ee1lIYNLeDDtOdzbQ6vhwCCmdYk QB7K5tlF9iBu8xpqvtIYL4kMPefqq+hX6edDzU0hS7906Bq2W8PQn1GzuqrXz3ol03du zpdOgFpFPUEhNJMbH991yYhzv/L1PkYcUs4yWE7DHHYu5ADGQb/2JhF/AbBE9u8EuhKT pPuu/mtyRxqs6gK0Aa6y0yULKrE/cTks+jno6e4oLJmfka3NEnbTE06LWphHOgVpsFj2 CyNg== X-Gm-Message-State: APjAAAXFVC7qTi5NTKnvE85DVDqGkhSnANoLNuWkO8m1I4GTtNzelKQr 2l4X7brWjQoAs68N+M/3mSeJPA== X-Google-Smtp-Source: APXvYqyNH4NYlDZcwbKIll05NR0WQTDgL47PpyR1MTUIPuI9tyAq8g/V8htHZ+Rmx9uzE8KFyLzzEg== X-Received: by 2002:a62:6c88:: with SMTP id h130mr14703771pfc.106.1557500342697; Fri, 10 May 2019 07:59:02 -0700 (PDT) Received: from hermes.lan (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id s17sm7013125pfm.149.2019.05.10.07.59.02 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 10 May 2019 07:59:02 -0700 (PDT) Date: Fri, 10 May 2019 07:58:55 -0700 From: Stephen Hemminger <stephen@networkplumber.org> To: "Eads, Gage" <gage.eads@intel.com> Cc: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>, "olivier.matz@6wind.com" <olivier.matz@6wind.com>, "arybchenko@solarflare.com" <arybchenko@solarflare.com>, "Richardson, Bruce" <bruce.richardson@intel.com>, "Ananyev, Konstantin" <konstantin.ananyev@intel.com>, "Honnappa.Nagarahalli@arm.com" <Honnappa.Nagarahalli@arm.com>, "gavin.hu@arm.com" <gavin.hu@arm.com>, "Ola.Liljedahl@arm.com" <Ola.Liljedahl@arm.com>, "nd@arm.com" <nd@arm.com> Message-ID: <20190510075855.2899716e@hermes.lan> In-Reply-To: <9184057F7FC11744A2107296B6B8EB1E68CB470E@fmsmsx101.amr.corp.intel.com> References: <20190118153117.23810-1-gage.eads@intel.com> <20190201143623.31135-1-gage.eads@intel.com> <1845234.OyIqJ6yfKh@xps> <9184057F7FC11744A2107296B6B8EB1E68CB470E@fmsmsx101.amr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v4] doc: announce ring API change X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> Message-ID: <20190510145855.lRR_cPqbiFVM8Q-DPmx8PKnuIVCE-0axs-a5BeFUIo4@z> On Fri, 10 May 2019 14:53:56 +0000 "Eads, Gage" <gage.eads@intel.com> wrote: > > 01/02/2019 15:36, Gage Eads: > > > In order to support the non-blocking ring[1], an API change > > > (additional argument to rte_ring_get_memsize()) is required in > > > librte_ring. This commit updates the deprecation notice to pave the > > > way for its inclusion in 19.08. > > > > > > [1] http://mails.dpdk.org/archives/dev/2019-January/124162.html > > > > > > Signed-off-by: Gage Eads <gage.eads@intel.com> > > > > There is still no agreement on this change? > > > > Still none. I was hoping this discussion (http://mails.dpdk.org/archives/dev/2019-April/129229.html) would lead to some clear direction, but at this point the effort is stalled. The fundamental tradeoff is between non-blocking rings and ABI breakage. Why not have a new ring type for non-blocking rings since non-blocking rings are not necessary for all use cases.