From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: "Burakov,
Anatoly"
<anatoly.burakov-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH RFC] eal: change core mask input format
Date: Fri, 23 May 2014 10:44:20 +0200 [thread overview]
Message-ID: <3072912.3LAuKXU4by@xps13> (raw)
In-Reply-To: <C6ECDF3AB251BE4894318F4E45123697592AAF7E-kPTMFJFq+rF9qrmMLTLiibfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Hi Anatoly,
2014-05-01 15:43, Burakov, Anatoly:
> > From: Didier Pallard <didier.pallard-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
> >
> > In current version, coremask can only be specified using a bitmask.
> > It will now be possible to specify core masks in 2 different ways:
> > - Using a bitmask (-c 0xnnn): bitmask must be in hex format and start with
> > 0x - Using a core set description in following format: -c
> > [c1[-c2]][,c3[-c4]]...
> >
> > -c 0-7,16-23,31 being equivalent to -c 0x80FF00FF
> >
> > Signed-off-by: Didier Pallard <didier.pallard-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
>
> Can we perhaps use a different parameter for that? E.g.
> --use-cores=[c1[-c2]][,c3[-c4]]... instead of -c?
I don't understand what would be improved by adding a new parameter.
I think being able to handle the 2 syntaxes within the same option is nice.
--
Thomas
next prev parent reply other threads:[~2014-05-23 8:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 14:14 [PATCH RFC] eal: change core mask input format David Marchand
[not found] ` <1398867282-15076-1-git-send-email-david.marchand-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2014-05-01 15:43 ` Burakov, Anatoly
[not found] ` <C6ECDF3AB251BE4894318F4E45123697592AAF7E-kPTMFJFq+rF9qrmMLTLiibfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-05-23 8:44 ` Thomas Monjalon [this message]
2014-05-23 9:02 ` Burakov, Anatoly
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=3072912.3LAuKXU4by@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=anatoly.burakov-ral2JQCrhuEAvxtiuMwx3w@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.