From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f52.google.com (mail-oi0-f52.google.com [209.85.218.52]) by dpdk.org (Postfix) with ESMTP id 1D8415946 for ; Mon, 1 Aug 2016 23:19:40 +0200 (CEST) Received: by mail-oi0-f52.google.com with SMTP id j185so209993028oih.0 for ; Mon, 01 Aug 2016 14:19:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=tReufC58V/4l8kCOn96Q17UbB+bPWmkswPthceW+0qk=; b=NIcwWhaFEqSIqFNFOlhGnQNO57ohymkiPQ4mJR9bpX6ZakR+MK1wqRLSoUtMPOCYR7 S3sFw8Ogh6gfhD9d6ebS+cFumUz7pDEEOMyuQNJhUOFS2FBTdCkNXOJ3JJ9Y47bh9COm HqVgQEl3TouMIFhzEUV7qpVOaQ7CXy1QB3aYL+4s/geUO1GPYJSALwDfOcsqe3abJseO KWX/98Qb+1E9wzkBi8sbc7U12xFK34zqT+LH7k2KSyedhnDNGpl3Itza5JQvmSZNG+g/ taC2+RfRmdOzuLOMATbebBNbX9d3CwfF3Y/MDyAn/27BTbjZfDSbmEEIeoijwvRWU3di ay/Q== 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; bh=tReufC58V/4l8kCOn96Q17UbB+bPWmkswPthceW+0qk=; b=jYkeyvewjK+2JBpdxG5cZUcGw9W0VCiIJb4gmlcpZZA3A63oVIxwnlXEhAJukfPy/a iXbMwfCICh/vARgNnUNgTda6im1bi43aT4ZdrIIcsmgfxGOXjG+JZ9A0p8fWNI8DQZWK yGIcmTIULvuX0+mIkxEtqP9S3l++Fq1iSG5jkloZGFGSqdJEydML/ov1gtx/BNg3RPb+ EDc88JUySf1JjwSg4Ga2mhQSzjkvU76tk8hYRyEnY478pf6UudaSW6IK5Oeg9y/3EENs iIIvHJ+tkbF9+mEMKNs7g0rZaNCcQq07vML7HAmOGCf7lM8Y9WfdjN1Agq+BOE12v25h OYCQ== X-Gm-Message-State: AEkoouuk9Jp3X7s+MKFMmNPukxkJj4yae12zZLPi+B+8VqjQeo5pFmbUpx7uXm5XSGcvxF84sjN/L6vKNYiMEw== X-Received: by 10.202.48.148 with SMTP id w142mr31424347oiw.181.1470086379407; Mon, 01 Aug 2016 14:19:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.24.7 with HTTP; Mon, 1 Aug 2016 14:19:38 -0700 (PDT) In-Reply-To: References: From: Gopakumar Choorakkot Edakkunni Date: Mon, 1 Aug 2016 14:19:38 -0700 Message-ID: To: dev@dpdk.org, olivier.matz@6wind.com Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] dpdk 16.07, issues with rte_mempool_create and rte_kni_alloc() 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, 01 Aug 2016 21:19:40 -0000 Well, for my purpose I just ended up creating a seperate/smaller pool earlier during bootup to try to guarantee its from one memseg. But I am assuming that this KNI restriction is something thats "currently" not fixed and is "fixable" ? Any ideas on what the summary of the reason for this restriction is - I was gonna check if I can fix that Rgds, Gopa. On Sat, Jul 30, 2016 at 10:39 PM, Gopakumar Choorakkot Edakkunni < gopakumar.c.e@gmail.com> wrote: > Hi all, > > So 16.07 seems to have an rte_mempool_create() which can allocate items > from multiple memzones (commit d1d914eb), which is awesome and is the > reason I upgraed to 16.07 !! > > But .. when I call rte_kni_alloc() with the mempool as parameter, theres a > check in there which says below > > /* KNI currently requires to have only one memory chunk */ > if (mp->nb_mem_chunks != 1) > goto kni_fail; > > And I hit that check because I am allocating a large mempool that happens > to span multiple memzones. I am perfectly fine with allocating a seperate > mempool just for KNI, except that I am unable to find any API or a flag or > some setting which says "create me a mempool that doesnt span memzones", > just so that I can use it with rte_kni_alloc() > > Any suggestions will be helpful ! > > Rgds, > Gopa. > >