From: Alex Markuze <alex@weka.io>
To: Wenji Wu <wenji@fnal.gov>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK memory mechanism
Date: Sun, 3 Aug 2014 11:41:29 +0300 [thread overview]
Message-ID: <CAKfHP0WZG6NR852o=Rnubz4RKx8-F6ozq-NK9vQJMyHPynYytg@mail.gmail.com> (raw)
In-Reply-To: <D00168AE.C6D6%wenji@fnal.gov>
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” pinned to avoid being swapped out? I checked the source code, and found there is API called “rte_mem_lock_page”. But it seems this API is never by called. Do I miss something?
>
> Thanks,
>
> wenji
>
>
>
>
prev parent reply other threads:[~2014-08-03 8:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 20:54 Wenji Wu
2014-08-03 8:41 ` Alex Markuze [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKfHP0WZG6NR852o=Rnubz4RKx8-F6ozq-NK9vQJMyHPynYytg@mail.gmail.com' \
--to=alex@weka.io \
--cc=dev@dpdk.org \
--cc=wenji@fnal.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).