DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ravi Kerur <rkerur@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 6/6] Move common functions in eal_memory.c
Date: Mon, 05 Jan 2015 13:17:23 -0800 (PST)	[thread overview]
Message-ID: <5340807.22YuSvaAXs@xps13> (raw)
In-Reply-To: <1419957440-11767-6-git-send-email-rkerur@gmail.com>

2014-12-30 11:37, Ravi Kerur:
> Use common function names rte_eal_hugepage_init and
> rte_eal_hugepage_attach for BSD and Linux.

I'd like to be sure that using hugepage wording instead of contigmem
is not too weird for BSD people.
Do not forget that we have a kernel module called contigmem.
Here, an ifdef or a wrapper seems appropriate to keep right wording.

-- 
Thomas

  reply	other threads:[~2015-01-05 21:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-30 16:36 [dpdk-dev] [PATCH v3 0/6] Move EAL common functions Ravi Kerur
2014-12-30 16:37 ` [dpdk-dev] [PATCH v3 1/6] Move common functions in eal_debug.c Ravi Kerur
2014-12-30 16:37   ` [dpdk-dev] [PATCH v3 2/6] Move common functions in eal_thread.c Ravi Kerur
2014-12-30 16:37   ` [dpdk-dev] [PATCH v3 3/6] Move common functions in eal.c Ravi Kerur
2014-12-30 16:37   ` [dpdk-dev] [PATCH v3 4/6] Move common functions in eal_lcore.c Ravi Kerur
2014-12-30 16:37   ` [dpdk-dev] [PATCH v3 5/6] Move common functions in eal_timer.c Ravi Kerur
2015-01-05 21:09     ` Thomas Monjalon
2014-12-30 16:37   ` [dpdk-dev] [PATCH v3 6/6] Move common functions in eal_memory.c Ravi Kerur
2015-01-05 21:17     ` Thomas Monjalon [this message]
2015-01-06 17:32       ` Ravi Kerur
2014-12-30 21:03 ` [dpdk-dev] [PATCH v3 0/6] Move EAL common functions Neil Horman

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=5340807.22YuSvaAXs@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=rkerur@gmail.com \
    /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).