From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Keith Wiles <keith.wiles@intel.com>
Cc: dev@dpdk.org, iryzhov@nfware.com
Subject: Re: [dpdk-dev] [PATCH v2 00/11] moving away from coremask to corelist
Date: Fri, 10 Feb 2017 09:46:35 +0100 [thread overview]
Message-ID: <2782356.hAb1fhpyXq@xps13> (raw)
In-Reply-To: <20170209234233.63333-1-keith.wiles@intel.com>
Hi Keith,
2017-02-09 17:42, Keith Wiles:
> The coremask option in DPDK is difficult to use and we should be
> promoting the use of the corelist (-l) option. The patch series
> adjusts the docs to use -l EAL option instead of the -c option.
>
> The patch series doc change only and is not required to be done
> in 17.02 release, but should be added to the 17.05 release.
> The -c option will be kept and not removed for now unless in the
> future we decide to deprecate the code.
>
> v2 - Fix taskset back to using -c
>
> Keith Wiles (11):
> doc/cryptodev: use corelist instead of coremask
> doc/faq: use corelist instead of coremask
> doc/freebsd: use corelist instead of coremask
> doc/howto: use corelist instead of coremask
> doc/linux: use corelist instead of coremask
> doc/nics: use corelist instead of coremask
> doc/prog_guide: use corelist instead of coremask
> doc/testpmd: use corelist instead of coremask
> doc/cryptoperf: use corelist instead of coremask
> doc/xen: use corelist instead of coremask
> doc/sample_app: use corelist instead of coremask
In case you make new revisions, I think you can squash every patches
in a single one. They are all doing the same thing in different files.
next prev parent reply other threads:[~2017-02-10 8:46 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 18:14 [dpdk-dev] [PATCH " Keith Wiles
2017-02-09 18:14 ` [dpdk-dev] [PATCH 01/11] doc/cryptodev: use corelist instead of coremask Keith Wiles
2017-02-09 18:14 ` [dpdk-dev] [PATCH 02/11] doc/faq: " Keith Wiles
2017-02-09 18:14 ` [dpdk-dev] [PATCH 03/11] doc/freebsd: " Keith Wiles
2017-02-09 18:14 ` [dpdk-dev] [PATCH 04/11] doc/howto: " Keith Wiles
2017-02-09 23:00 ` Igor Ryzhov
2017-02-09 23:20 ` Wiles, Keith
2017-02-09 18:14 ` [dpdk-dev] [PATCH 05/11] doc/linux: " Keith Wiles
2017-02-09 18:14 ` [dpdk-dev] [PATCH 06/11] doc/nics: " Keith Wiles
2017-02-09 18:14 ` [dpdk-dev] [PATCH 07/11] doc/prog_guide: " Keith Wiles
2017-02-09 18:14 ` [dpdk-dev] [PATCH 08/11] doc/testpmd: " Keith Wiles
2017-02-09 18:14 ` [dpdk-dev] [PATCH 09/11] doc/cryptoperf: " Keith Wiles
2017-02-09 18:14 ` [dpdk-dev] [PATCH 10/11] doc/xen: " Keith Wiles
2017-02-09 18:14 ` [dpdk-dev] [PATCH 11/11] doc/sample_app: " Keith Wiles
2017-02-09 23:42 ` [dpdk-dev] [PATCH v2 00/11] moving away from coremask to corelist Keith Wiles
2017-02-10 8:46 ` Thomas Monjalon [this message]
2017-02-10 13:47 ` Wiles, Keith
2017-02-09 23:42 ` [dpdk-dev] [PATCH v2 01/11] doc/cryptodev: use corelist instead of coremask Keith Wiles
2017-02-09 23:42 ` [dpdk-dev] [PATCH v2 02/11] doc/faq: " Keith Wiles
2017-02-09 23:42 ` [dpdk-dev] [PATCH v2 03/11] doc/freebsd: " Keith Wiles
2017-02-09 23:42 ` [dpdk-dev] [PATCH v2 04/11] doc/howto: " Keith Wiles
2017-02-09 23:42 ` [dpdk-dev] [PATCH v2 05/11] doc/linux: " Keith Wiles
2017-02-09 23:42 ` [dpdk-dev] [PATCH v2 06/11] doc/nics: " Keith Wiles
2017-02-09 23:42 ` [dpdk-dev] [PATCH v2 07/11] doc/prog_guide: " Keith Wiles
2017-02-09 23:42 ` [dpdk-dev] [PATCH v2 08/11] doc/testpmd: " Keith Wiles
2017-02-09 23:42 ` [dpdk-dev] [PATCH v2 09/11] doc/cryptoperf: " Keith Wiles
2017-02-09 23:42 ` [dpdk-dev] [PATCH v2 10/11] doc/xen: " Keith Wiles
2017-02-09 23:42 ` [dpdk-dev] [PATCH v2 11/11] doc/sample_app: " Keith Wiles
2017-02-10 14:01 ` [dpdk-dev] [PATCH v3] doc: " Keith Wiles
2017-02-21 15:53 ` Mcnamara, John
2017-02-21 17:38 ` [dpdk-dev] [PATCH v4] " Keith Wiles
2017-02-22 10:20 ` Mcnamara, John
2017-02-27 19:13 ` [dpdk-dev] [PATCH v5] " Keith Wiles
2017-02-28 17:14 ` Mcnamara, John
2017-03-01 19:40 ` Thomas Monjalon
2017-03-01 20:03 ` Wiles, Keith
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=2782356.hAb1fhpyXq@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=iryzhov@nfware.com \
--cc=keith.wiles@intel.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).