From: Adrien Mazarguil <adrien.mazarguil-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Damien Millescamps
<damien.millescamps-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH 2/2] mem: fix mempool for --no-huge
Date: Fri, 26 Jul 2013 16:59:32 +0200 [thread overview]
Message-ID: <20130726145932.GO7849@6wind.com> (raw)
In-Reply-To: <be4886be27e09d0f0fa1a81be866b99bbab4f081.1374849076.git.damien.millescamps-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
On Fri, Jul 26, 2013 at 04:39:13PM +0200, Damien Millescamps wrote:
> In --no-huge mode, mempool provides objects with their associated
> header/trailer fitting in a standard page (usually 4KB).
> This means all non-UIO driver should work correctly in this mode,
> since UIO drivers allocate ring sizes that cannot fit in a page.
>
> Extend rte_mempool_virt2phy to obtain the correct physical address when
> elements of the pool are not on the same physically contiguous memory region.
> This is a first step for enhancement PR #29696.
>
> Reason for this patch is to be able to run on a kernel < 2.6.37 without
> the need to patch it, since all kernel below are either bugged or don't
> have huge page support at all (< 2.6.28).
>
> Signed-off-by: Damien Millescamps <damien.millescamps-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
> ---
> lib/librte_eal/linuxapp/eal/eal_memory.c | 2 +-
> lib/librte_mempool/rte_mempool.c | 54 +++++++++++++++++++++++++++++-
> lib/librte_mempool/rte_mempool.h | 20 +++++++----
> 3 files changed, 67 insertions(+), 9 deletions(-)
Acked-by: Adrien Mazarguil <adrien.mazarguil-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
--
Adrien Mazarguil
6WIND
next prev parent reply other threads:[~2013-07-26 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 14:39 [PATCH 0/2] fix mempool when --no-huge option is set Damien Millescamps
[not found] ` <cover.1374849076.git.damien.millescamps-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-07-26 14:39 ` [PATCH 1/2] mem: get hugepages config Damien Millescamps
[not found] ` <0e095118447ebbd42f2762edbda8218b13b58a1a.1374849076.git.damien.millescamps-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-07-26 14:59 ` Adrien Mazarguil
[not found] ` <20130726145912.GN7849-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-07-26 15:10 ` Thomas Monjalon
2013-07-26 14:39 ` [PATCH 2/2] mem: fix mempool for --no-huge Damien Millescamps
[not found] ` <be4886be27e09d0f0fa1a81be866b99bbab4f081.1374849076.git.damien.millescamps-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-07-26 14:59 ` Adrien Mazarguil [this message]
[not found] ` <20130726145932.GO7849-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-07-26 15:10 ` Thomas Monjalon
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=20130726145932.GO7849@6wind.com \
--to=adrien.mazarguil-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=damien.millescamps-pdR9zngts4EAvxtiuMwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.