* [dpdk-dev] [PATCH] crypto/scheduler: update documenation for multicore scheduler
@ 2017-07-18 11:32 Kirill Rybalchenko
2017-07-18 13:48 ` De Lara Guarch, Pablo
2017-07-18 14:21 ` De Lara Guarch, Pablo
0 siblings, 2 replies; 3+ messages in thread
From: Kirill Rybalchenko @ 2017-07-18 11:32 UTC (permalink / raw)
To: roy.fan.zhang, declan.doherty; +Cc: dev, Kirill Rybalchenko
Done more clear explanation of usage of corelist parameter.
Signed-off-by: Kirill Rybalchenko <kirill.rybalchenko@intel.com>
---
doc/guides/cryptodevs/scheduler.rst | 2 ++
1 file changed, 2 insertions(+)
diff --git a/doc/guides/cryptodevs/scheduler.rst b/doc/guides/cryptodevs/scheduler.rst
index f3ee88a..3ba0188 100644
--- a/doc/guides/cryptodevs/scheduler.rst
+++ b/doc/guides/cryptodevs/scheduler.rst
@@ -191,6 +191,8 @@ operation:
* corelist: Semicolon-separated list of logical cores to be used as workers.
The number of worker cores should be equal to the number of slave cryptodevs.
+ Be sure that all worker cores are present in EAL core list parameter and
+ are not used by application or any other process.
Example:
... --vdev "crypto_aesni_mb1,name=aesni_mb_1" --vdev "crypto_aesni_mb_pmd2,name=aesni_mb_2" \
--
2.5.5
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] [PATCH] crypto/scheduler: update documenation for multicore scheduler
2017-07-18 11:32 [dpdk-dev] [PATCH] crypto/scheduler: update documenation for multicore scheduler Kirill Rybalchenko
@ 2017-07-18 13:48 ` De Lara Guarch, Pablo
2017-07-18 14:21 ` De Lara Guarch, Pablo
1 sibling, 0 replies; 3+ messages in thread
From: De Lara Guarch, Pablo @ 2017-07-18 13:48 UTC (permalink / raw)
To: Rybalchenko, Kirill, Zhang, Roy Fan, Doherty, Declan
Cc: dev, Rybalchenko, Kirill
Hi Kirill,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Kirill Rybalchenko
> Sent: Tuesday, July 18, 2017 12:32 PM
> To: Zhang, Roy Fan <roy.fan.zhang@intel.com>; Doherty, Declan
> <declan.doherty@intel.com>
> Cc: dev@dpdk.org; Rybalchenko, Kirill <kirill.rybalchenko@intel.com>
> Subject: [dpdk-dev] [PATCH] crypto/scheduler: update documenation for
> multicore scheduler
>
> Done more clear explanation of usage of corelist parameter.
>
> Signed-off-by: Kirill Rybalchenko <kirill.rybalchenko@intel.com>
Title should be something like: "doc: extend info on multi-core scheduler".
Will fix that for you when merging.
Thanks,
Pablo
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [dpdk-dev] [PATCH] crypto/scheduler: update documenation for multicore scheduler
2017-07-18 11:32 [dpdk-dev] [PATCH] crypto/scheduler: update documenation for multicore scheduler Kirill Rybalchenko
2017-07-18 13:48 ` De Lara Guarch, Pablo
@ 2017-07-18 14:21 ` De Lara Guarch, Pablo
1 sibling, 0 replies; 3+ messages in thread
From: De Lara Guarch, Pablo @ 2017-07-18 14:21 UTC (permalink / raw)
To: Rybalchenko, Kirill, Zhang, Roy Fan, Doherty, Declan
Cc: dev, Rybalchenko, Kirill
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Kirill Rybalchenko
> Sent: Tuesday, July 18, 2017 12:32 PM
> To: Zhang, Roy Fan <roy.fan.zhang@intel.com>; Doherty, Declan
> <declan.doherty@intel.com>
> Cc: dev@dpdk.org; Rybalchenko, Kirill <kirill.rybalchenko@intel.com>
> Subject: [dpdk-dev] [PATCH] crypto/scheduler: update documenation for
> multicore scheduler
>
> Done more clear explanation of usage of corelist parameter.
>
> Signed-off-by: Kirill Rybalchenko <kirill.rybalchenko@intel.com>
Applied to dpdk-next-crypto.
Thanks,
Pablo
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-07-18 14:21 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-07-18 11:32 [dpdk-dev] [PATCH] crypto/scheduler: update documenation for multicore scheduler Kirill Rybalchenko
2017-07-18 13:48 ` De Lara Guarch, Pablo
2017-07-18 14:21 ` De Lara Guarch, Pablo
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).