All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: "Chi,
	Xiaobo (NSN - CN/Hangzhou)"
	<xiaobo.chi-OYasijW0DpE@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH] add one option memory-only for those secondary PRBs
Date: Tue, 02 Dec 2014 11:01:03 +0100	[thread overview]
Message-ID: <2039360.IUUcaknktz@xps13> (raw)
In-Reply-To: <EF703E8970265941A1316EEFE0AA7B6C40A63042-vxsKAgvzMM8+o/1KEruIITjhXmbd+16H@public.gmane.org>

Hi,

2014-12-02 09:55, Chi, Xiaobo:
> Problem:
> Here, these DPDK based SECONDARY processes need only the DPDK's hugepage
> based sharememory mechanism and it's upper libs (such as ring, mempool,
> etc.), they need not cpu core pinning, iopl privilege changing , pci device,
> timer, alarm, interrupt, shared_driver_list,  core_info, threads for each
> core, etc. Then, for such kind of SECONDARY processes, the current
> rte_eal_init() is too heavy.  
> I have seen some others also met similar troubles. 
> 
> Solution:
> One new EAL initializing argument, --memory-only, is added. It is only for
> those SECONDARY processes which only want to share memory with primary
> process. When this argument is defined, users need not define those
> madentory arguments, such as "-c xx -n xx", due to we don't want to pin such
> kind of processes to any CPUs.

That's exactly the type of things that you should put in the commit log.
It misses also a Signed-off-by.
All guidelines are explained in this page:
	http://dpdk.org/dev#send

Please check your patch with checkpatch for indentation and other details.

-- 
Thomas

  parent reply	other threads:[~2014-12-02 10:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-02  9:41 [PATCH] add one option memory-only for those secondary PRBs chixiaobo
     [not found] ` <1417513268-6040-1-git-send-email-xiaobo.chi-OYasijW0DpE@public.gmane.org>
2014-12-02  9:55   ` Chi, Xiaobo (NSN - CN/Hangzhou)
     [not found]     ` <EF703E8970265941A1316EEFE0AA7B6C40A63042-vxsKAgvzMM8+o/1KEruIITjhXmbd+16H@public.gmane.org>
2014-12-02 10:01       ` Thomas Monjalon [this message]
2014-12-02 10:20   ` Bruce Richardson

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=2039360.IUUcaknktz@xps13 \
    --to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=xiaobo.chi-OYasijW0DpE@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.