From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <alex@weka.io>
Received: from mail-ob0-f169.google.com (mail-ob0-f169.google.com
 [209.85.214.169]) by dpdk.org (Postfix) with ESMTP id B916658E6
 for <dev@dpdk.org>; Sun,  3 Aug 2014 10:39:17 +0200 (CEST)
Received: by mail-ob0-f169.google.com with SMTP id nu7so3745496obb.14
 for <dev@dpdk.org>; Sun, 03 Aug 2014 01:41:30 -0700 (PDT)
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:date
 :message-id:subject:from:to:cc:content-type
 :content-transfer-encoding;
 bh=Gh8dSuYo7FbbtZ9pCnLINEVPFcyNkULy9YvcjUepgh4=;
 b=Tannjo6VUvRfXaikkzXQvI5+/7D+l0U+OolwplGuyV6Zt0m/at+9BwyK8znDw6aq1A
 /wSdSqWh7Sfyg2O+h9o2BxEbqQWAjqjdH1lSb8xtdTALEP5lNiNY86fL+mKJzb8TMcEB
 79tpKIzetvhyzqaQrXANKCUZqn2nk3Jv3mQDXNTadrKeHsyizeJjr3F/3WMK/ugsGoGs
 uzbeRGkGhxDDvwsUcPiM0ro/0FIdBFpDoVzMwNhMopPWBj+7TcK3a1fMnpHsK+9acDco
 vMRbTKVmYst887smhTCUo3vELBhrnqpRvvj0VvLjQDcuTXKPfqN1fTLlpp8aKrXgn7oz
 lINw==
X-Gm-Message-State: ALoCoQlE8Wt+nupemUqJngedpYhvyxg91jFPeStZv1b+iyo62nwc6A9HtKptAOUfUPWCcXz3CYl6
MIME-Version: 1.0
X-Received: by 10.182.191.7 with SMTP id gu7mr22254672obc.14.1407055289923;
 Sun, 03 Aug 2014 01:41:29 -0700 (PDT)
Received: by 10.202.55.198 with HTTP; Sun, 3 Aug 2014 01:41:29 -0700 (PDT)
In-Reply-To: <D00168AE.C6D6%wenji@fnal.gov>
References: <D00168AE.C6D6%wenji@fnal.gov>
Date: Sun, 3 Aug 2014 11:41:29 +0300
Message-ID: <CAKfHP0WZG6NR852o=Rnubz4RKx8-F6ozq-NK9vQJMyHPynYytg@mail.gmail.com>
From: Alex Markuze <alex@weka.io>
To: Wenji Wu <wenji@fnal.gov>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK memory mechanism
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Sun, 03 Aug 2014 08:39:18 -0000

I had several similar concerns a few weeks back, please look for this
email thread "Memory Pinning." On this mailing list.
Bruce was very helpful. Ill forward the thread to you now. Hope it helps.

On Fri, Aug 1, 2014 at 11:54 PM, Wenji Wu <wenji@fnal.gov> wrote:
> Hello, everybody,
>
> I am new on DPDK, and have several questions on DPDK.
>
> Is "Mbuf Pool=E2=80=9D pinned to avoid being swapped out? I checked the s=
ource code, and found there is API called =E2=80=9Crte_mem_lock_page=E2=80=
=9D. But it seems this API is never by called. Do I miss something?
>
> Thanks,
>
> wenji
>
>
>
>