From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2CACCC5DF60 for ; Fri, 8 Nov 2019 16:17:10 +0000 (UTC) Received: from dpdk.org (dpdk.org [92.243.14.124]) by mail.kernel.org (Postfix) with ESMTP id B85DB21882 for ; Fri, 8 Nov 2019 16:17:09 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=broadcom.com header.i=@broadcom.com header.b="DPbpFrUd" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B85DB21882 Authentication-Results: mail.kernel.org; dmarc=fail (p=quarantine dis=none) header.from=broadcom.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 373201C013; Fri, 8 Nov 2019 17:17:05 +0100 (CET) Received: from mail-il1-f196.google.com (mail-il1-f196.google.com [209.85.166.196]) by dpdk.org (Postfix) with ESMTP id 165651BF8B for ; Thu, 7 Nov 2019 17:17:01 +0100 (CET) Received: by mail-il1-f196.google.com with SMTP id z10so2308055ilo.8 for ; Thu, 07 Nov 2019 08:17:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MpRnYpcCuliwLGuZQ5ZDmJMtqDT+c+YDAKVi0e1Tv4Y=; b=DPbpFrUdlVxcDruP1MpC+kjXmXmAfxbu/dtbS8lWizmKSNO3PHbn+jsVOYmxYq4o3D IABW8RqgMLIHZHgYQzwPkPf/+1TGosuJco9EE75dzlSDHBVWKUp4avDnzPiwokhWAvSK vzQ9BWm/mhDtHKRr4T9Ffv+De5PRBrqBoWyok= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MpRnYpcCuliwLGuZQ5ZDmJMtqDT+c+YDAKVi0e1Tv4Y=; b=K2m09/O0tw0p8wtaHrGzcWCy9aLc+VU3gkmluI5E6yv3FgZ/oADSOwY3CRiwasbSX9 DjWm7zWSuDX6hWG7/VRySikAdF8RqrFBVs2iHJDpL6P2GRVsSm3/ieAE5UgtkB96oMev o8AwjBNuUbNSrlqD9rrlLZEHOcmxce4eZOqbF7a61nyhxuxjbr4/+yCAnT6zFqS3MGQ+ uUJOzMC/U/wA2RO4k5eTd9quV0Vm2xSrdBc0lzrWwbNrMWHL/2/81fDglikfBhDVuBWB +Ya27txeAPXjFywR/Moyz7TAtPvSBETCxoiEp3wP2aKhLV0cLjvMU6yq6MviGekaGdgL wyyQ== X-Gm-Message-State: APjAAAWtnTdg68GeL4qZt9EPS6AEixw6ehhkCarvZzdc3eyVUuCbfzp5 9TpW42GbMcc3z+4X1e5BsGX2SZW9BUzlbw6PQ2+T0g== X-Google-Smtp-Source: APXvYqydV/td2yODRk8KPKlcn9ePAsnpy9EJSWOW/DFrQ8h26Kn+vc7JTPwHVdiLfcKc2G7AAB1G9ns01r0uMdzkBSk= X-Received: by 2002:a92:4609:: with SMTP id t9mr5121678ila.156.1573143420172; Thu, 07 Nov 2019 08:17:00 -0800 (PST) MIME-Version: 1.0 References: <20191015053047.52260-1-ajit.khaparde@broadcom.com> <83009bb3-1e0c-a22e-eff8-41a437817cb7@intel.com> <64edebee-3686-beca-2b30-c6ec1f26c162@intel.com> <31bff5b7-169c-e158-3a87-6448272c571c@intel.com> <32f3cd1a-08bb-e4bc-c22c-53453b936dd3@intel.com> <3a954a3f-1fc5-47f0-64f2-a7c8e3fbf964@intel.com> In-Reply-To: From: Rajesh Ravi Date: Thu, 7 Nov 2019 21:46:23 +0530 Message-ID: To: David Marchand Cc: Ajit Khaparde , dev , Jonathan Richardson , Scott Branden , Vikram Mysore Prakash , Srinath Mannam , "Burakov, Anatoly" X-Mailman-Approved-At: Fri, 08 Nov 2019 17:17:01 +0100 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] [PATCH] eal: add option --iso-cmem for external custom 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Thanks David. With Anatoly's patch applied my patch is not needed as the purpose is solved. Regards, Rajesh On Thu, Nov 7, 2019 at 9:21 PM David Marchand wrote: > On Wed, Nov 6, 2019 at 2:55 PM David Marchand > wrote: > > > > On Tue, Nov 5, 2019 at 6:14 PM Burakov, Anatoly > > wrote: > > > > > > On 05-Nov-19 3:18 PM, Burakov, Anatoly wrote: > > > > On 05-Nov-19 2:10 PM, Rajesh Ravi wrote: > > > >> Thanks a lot Anatoly. > > > >> Will the same solution work with DPDK 19.02 as well? We 're > actually > > > >> using DPDK 19.02 for memory allocations for SPDK 19.07. > > > >> DPDK 19.11 may not be supported by SPDK 19.07 we 're currently > using. > > > >> > > > >> I 'll definitely test if the patch works with DPDK 19.02 > > > >> > > > >> Thanks again for your time and help. > > > >> > > > >> Regards, > > > >> Rajesh > > > > > > > > Hi Rajesh, > > > > > > > > Please test the patch [1] and see if it works for you. The patch is > not > > > > intended for 19.02 (in fact, 19.02 is not even supported any more), > but > > > > it may still apply. In the meantime, i'm working on a different patch > > > > for 18.11, that will achieve the same thing using different means. > > > > > > > > [1] http://patches.dpdk.org/patch/62468/ > > > > > > > > > > The following is an alternative implementation that is based off 18.11: > > > > > > http://patches.dpdk.org/patch/62486/ > > > > Thanks Rajesh, following your test report, I applied Anatoly patch. > A backport will go to 18.11. > > I will mark this current proposal as rejected. > If you think it should still be considered, then please set this patch > state back to new in patchwork and explain what is missing in this > thread. > > > Thanks. > -- > David Marchand > > -- Regards, Rajesh