On 2023-09-07 01:00, Stephen Hemminger wrote:
On Wed, 6 Sep 2023 22:02:54 +0200
Mattias Rönnblom wrote:
On 2023-09-06 19:20, Stephen Hemminger wrote:
Move the random number state into thread local storage.
Me and Morten discussed TLS versus other alternatives in some other
thread. The downs
Hello,
On Fri, Sep 8, 2023 at 8:42 AM Antón Rey Villaverde
wrote:
>
> Hi,
> I have a problem while trying to manage my physical Ethernet interface from
> DPDK (latest version compiled from source).
> I have a:
> NIC: :00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection
> (13)
On 2023-09-08 00:09, Sevincer, Abdullah wrote:
Hi Stephen,
It is probing ports for best CPU. Yes it collects cycles. We may rework in the
future.
Best, in what sense? Is this some kind of topology exploration? One DLB
port being closer to (cheaper to access for) certain cores?
Open to sugg
Hi, Pattan, Reshma
On 2023/9/6 0:29, Pattan, Reshma wrote:
-Original Message-
+ uint8_t *rss_key;
Instead of pointer can you just take key of type below, so u no need to do
dynamic memory allocation using malloc and free .
Ex: uint8_t hash_key[RSS_HASH_KEY_LENGTH];
Hi, Pattan, Reshma
On 2023/9/6 1:07, Pattan, Reshma wrote:
Instead of above function you can declare const array of strings as below to
map hash function names.
static const char * const hf_names[] = {
[RTE_ETH_HASH_FUNCTION_SIMPLE_XOR] = " simple_xor ",
[RTE_ETH_HASH_FUNCTI
This patchset is to support setting and querying RSS algorithms.
--
v4:
1. recomment some definitions related to RSS.
2. allocate static memory for rss_key instead of dynamic.
3. use array of strings to get the name of rss algorithm.
4. add display of rss algorithm with testpmd.
v3:
1. fix commit
1. Recomment fields of 'rte_eth_rss_conf'.
2. Add comments for RTE_ETH_HASH_FUNCTION_DEFAULT.
Signed-off-by: Jie Hai
---
lib/ethdev/rte_ethdev.h | 28 +---
lib/ethdev/rte_flow.h | 4
2 files changed, 17 insertions(+), 15 deletions(-)
diff --git a/lib/ethdev/rte_e
Currently, rte_eth_rss_conf supports configuring and querying
RSS hash functions, rss key and it's length, but not RSS hash
algorithm.
The structure ``rte_eth_rss_conf`` is extended by adding a new
field "func". This represents the RSS algorithms to apply. The
following API will be affected:
From: Huisong Li
Support setting and querying RSS hash function by ethdev ops.
Signed-off-by: Huisong Li
Signed-off-by: Dongdong Liu
---
drivers/net/hns3/hns3_rss.c | 47 +
1 file changed, 27 insertions(+), 20 deletions(-)
diff --git a/drivers/net/hns3/hns
Command show-port should show RSS info (rss_key, len and rss_hf),
However, the information is shown only when rss_conf.rss_key is not
NULL. Since no memory is allocated for rss_conf.rss_key, rss_key
will always be NULL and the rss_info will never show. This patch
allocates memory for rss_conf.rss_k
This patch splits the length and value of RSS key into two parts,
removes spaces between RSS keys, and adds line breaks between RSS
key and RSS hf.
Before the adjustment, RSS info is shown as:
- RSS
-- RSS len 40 key (hex): 6d 5a 56 da 25 5b e c2 41 67 \
25 3d 43 a3 8f b0
Add the command "show port X rss-hash func" to display the RSS hash
algorithms of port X. An example is shown:
testpmd> show port 0 rss-hash func
RSS algorithms:
toeplitz
Signed-off-by: Jie Hai
---
app/test-pmd/cmdline.c | 29 -
app/test-pmd/config.c | 36
Display RSS hash algorithm with command show-port as below.
- RSS info
-- hash algorithm : toeplitz
Signed-off-by: Jie Hai
Signed-off-by: Dongdong Liu
---
app/proc-info/main.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/app/proc-info/main.c b/app/proc-info/main.c
in
Hi, Thomas
Thanks for your review.
On 2023/9/4 15:45, Thomas Monjalon wrote:
04/09/2023 09:10, Jie Hai:
On 2023/8/30 19:46, Thomas Monjalon wrote:
26/08/2023 09:46, Jie Hai:
>> + * The *func* field of the *rss_conf* structure indicates the hash
algorithm
+ * applied by the RSS hashing. Pa
Hi, thanks for the quick response and the feedback.
*> Afaics, this nic is not supported by DPDK drivers.*
Indeed there is nothing about "15fb" (the PCI ID of my NIC) in the output
of ./usertools/dpdk-pmdinfo.py build/app/dpdk-testpmd , so I guess it is
not supported.
On the other hand, I do see
On Fri, Sep 8, 2023 at 11:05 AM Antón Rey Villaverde
wrote:
> > Afaics, this nic is not supported by DPDK drivers.
>
> Indeed there is nothing about "15fb" (the PCI ID of my NIC) in the output of
> ./usertools/dpdk-pmdinfo.py build/app/dpdk-testpmd , so I guess it is not
> supported.
>
> On the
The send to kernel action was supported in NIC and FDB tables,
Currently[1], the send to kernel action is created in NIC RX only.
With some TC rules (example: roce packets, redirects into rep ports)
and DPDK RTE rules for the rest of the traffic. Then it needs the
specific rule to re-route the pac
The send to kernel action was supported in NIC and FDB tables,
Currently, the send to kernel action is created in NIC RX only.
With some TC rules (example: roce packets, redirects into rep ports)
and DPDK RTE rules for the rest of the traffic. Then it needs the
specific rule to re-route the packet
The hws send to kernel action was supported in NIC and FDB tables,
Currently, the send to kernel action is created in NIC RX only.
This patch adds the FDB and NIC-TX tables support for sending to the kernel
action for HWS.
Signed-off-by: Jiawei Wang
---
drivers/net/mlx5/mlx5.h | 2 +-
This patch adds the description for send to kernel action support.
Signed-off-by: Jiawei Wang
Acked-by: Ori Kam
---
doc/guides/nics/mlx5.rst | 7 +++
doc/guides/prog_guide/rte_flow.rst | 9 +
lib/ethdev/rte_flow.h | 1 -
3 files changed, 16 insertions(+), 1 de
Hi, Stephen Hemminger
On 2023/9/6 23:10, Stephen Hemminger wrote:
On Sat, 26 Aug 2023 15:46:03 +0800
Jie Hai wrote:
Currently, rte_eth_rss_conf supports configuring and querying
rss hash functions, rss key and it's length, but not rss hash
algorithm.
The structure ``rte_eth_rss_conf`` is ext
> -Original Message-
> From: Jiawei(Jonny) Wang
> Sent: Friday, September 8, 2023 5:21 PM
> To: Suanming Mou ; Ori Kam ;
> NBU-Contact-Thomas Monjalon (EXTERNAL)
> Cc: dev@dpdk.org; Raslan Darawsheh
> Subject: [PATCH 1/3] net/mlx5: extend send to kernel action support
>
> The send to
> -Original Message-
> From: Jiawei(Jonny) Wang
> Sent: Friday, September 8, 2023 5:21 PM
> To: Suanming Mou ; Ori Kam ;
> NBU-Contact-Thomas Monjalon (EXTERNAL)
> Cc: dev@dpdk.org; Raslan Darawsheh
> Subject: [PATCH 2/3] net/mlx5: extend hws send to kernel action support
>
> The hws
This patch replaces flex Tx descriptor with base Tx descriptor to align
with kernel driver practice.
Signed-off-by: Simei Su
---
v3:
* Change context TSO descriptor from base mode to flex mode.
v2:
* Refine commit title and commit log.
* Remove redundant definition.
* Modify base mode context TS
> -Original Message-
> From: Anoob Joseph
> Sent: Friday, September 8, 2023 6:40 AM
> To: Akhil Goyal ; Power, Ciara
> Cc: Jerin Jacob ; dev@dpdk.org
> Subject: [PATCH 1/4] security: remove redundant cast
>
> The API 'rte_cryptodev_get_sec_ctx' returns void *. Type cast is not require
From: Sunil Kumar Kori
Current l3fwd-graph application only validates l3fwd use case.
To scale up this, new application will be added with a framework
to run as user's provided usecases.
Required configuration and use cases details are fetched via a
static .cli file which will be used to create
Hello everyone,
As per proposed CLIs to configure graph for different use cases, v3 is
implemented under the following request:
https://patches.dpdk.org/project/dpdk/patch/20230908104907.4060511-1-sk...@marvell.com/
Please take look on and provide feedback.
Regards
Sunil Kumar Kori
> -Origi
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state,
for example,
[1] 5028f207a4fa ("app/testpmd: fix
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the driver needs to modify the queue st
Here's how the problem arises.
step1: Start the app.
dpdk-testpmd -a :35:00.0 -l 0-3 -- -i --rxq=10 --txq=10
step2: Perform the following steps and send traffic. As expected,
queue 7 does not send or receive packets, and other queues do.
port 0 rxq 7 stop
port 0 txq 7 stop
set
On Fri, Sep 8, 2023 at 1:32 PM Jie Hai wrote:
>
> The DPDK framework reports the queue state, which is stored in
> dev->data->tx_queue_state and dev->data->rx_queue_state. The
> state is maintained by the driver. Users may determine whether
> a queue participates in packet forwarding based on the
SDAP header when enabled needs to be authenticated but not encrypted.
Signed-off-by: Aakash Sasidharan
---
lib/pdcp/pdcp_entity.h | 2 ++
lib/pdcp/pdcp_process.c | 22 --
2 files changed, 18 insertions(+), 6 deletions(-)
diff --git a/lib/pdcp/pdcp_entity.h b/lib/pdcp/pdcp_
Add PDCP SDAP test cases.
Signed-off-by: Aakash Sasidharan
---
app/test/test_pdcp.c | 438 +++
1 file changed, 397 insertions(+), 41 deletions(-)
diff --git a/app/test/test_pdcp.c b/app/test/test_pdcp.c
index 6c73c1db36..9c9e7a51fc 100644
--- a/app/test/t
Add PDCP SDAP combined mode tests.
Signed-off-by: Aakash Sasidharan
---
app/test/test_pdcp.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/app/test/test_pdcp.c b/app/test/test_pdcp.c
index 9c9e7a51fc..5f8ec08e32 100644
--- a/app/test/test_pdcp.c
+++ b/app/test/test_pdcp.c
@@ -2275,6 +22
On 9/8/23 14:28, Jie Hai wrote:
The DPDK framework reports the queue state, which is stored in
dev->data->tx_queue_state and dev->data->rx_queue_state. The
state is maintained by the driver. Users may determine whether
a queue participates in packet forwarding based on the state.
Therefore, the d
The issue arose due to the change in the DPDK read-write lock
implementation. That change added a new flag, RTE_RWLOCK_WAIT, designed
to prevent new read locks while a write lock is in the queue. However,
this change has led to a scenario where a recursive read lock, where a
lock is acquired twice
The issue arose due to changes in the DPDK read-write lock
implementation. Following these changes, the RW-lock no longer supports
recursion, implying that a single thread shouldn't obtain a read lock if
it already possesses one. The problem arises during initialization: the
rte_eal_init() function
Implementing a lock annotation for rte_memseg_list_walk() to
proactively identify bugs similar to memory_hotplug_lock deadlock during
initialization during compile time.
Bugzilla ID: 1277
Signed-off-by: Artemy Kovalyov
---
lib/eal/common/eal_memalloc.h | 3 ++-
lib/eal/common/eal_priva
> -Original Message-
> From: Richardson, Bruce
> Sent: Monday, September 4, 2023 5:38 PM
> To: Van Haaren, Harry
> Cc: dev@dpdk.org
> Subject: Re: [PATCH 2/2] event/sw: fix ordering corruption with op release
> > drivers/event/sw/sw_evdev_scheduler.c | 45 ---
>
On 2023-09-07 17:24, Stephen Hemminger wrote:
Add missing locking so that if two non-EAL threads call rte_rand()
they will not corrupt the per-thread state.
Fixes: 3f002f069612 ("eal: replace libc-based random generation with LFSR")
The API documentation clearly states that no MT safety guaran
On Fri, 8 Sep 2023 22:48:54 +0200
Mattias Rönnblom wrote:
> On 2023-09-07 17:24, Stephen Hemminger wrote:
> > Add missing locking so that if two non-EAL threads call rte_rand()
> > they will not corrupt the per-thread state.
> >
> > Fixes: 3f002f069612 ("eal: replace libc-based random generation
On Fri, 8 Sep 2023 17:28:08 +0800
Jie Hai wrote:
> Hi, Stephen Hemminger
>
> On 2023/9/6 23:10, Stephen Hemminger wrote:
> > On Sat, 26 Aug 2023 15:46:03 +0800
> > Jie Hai wrote:
> >
> >> Currently, rte_eth_rss_conf supports configuring and querying
> >> rss hash functions, rss key and it's
On Fri, Sep 8, 2023 at 1:44 AM Jie Hai wrote:
>
> Hi, Thomas
> Thanks for your review.
>
> On 2023/9/4 15:45, Thomas Monjalon wrote:
> > 04/09/2023 09:10, Jie Hai:
> >> On 2023/8/30 19:46, Thomas Monjalon wrote:
> >>> 26/08/2023 09:46, Jie Hai:
> > >> + * The *func* field of the *rss_conf* struc
06/09/2023 21:02, Mattias Rönnblom пишет:
On 2023-09-06 19:20, Stephen Hemminger wrote:
Move the random number state into thread local storage.
Me and Morten discussed TLS versus other alternatives in some other
thread. The downside of TLS that Morten pointed out, from what I recall,
is that
Please see inline.
> -Original Message-
> From: sk...@marvell.com
> Sent: Friday, September 8, 2023 4:19 PM
> To: Thomas Monjalon ; Sunil Kumar Kori
> ;
> Rakesh Kudurumalla
> Cc: dev@dpdk.org
> Subject: [EXT] [PATCH v3 1/1] app/graph: add example for different usecases
>
> External Em
> -Original Message-
> From: Xing, Beilei
> Sent: Friday, September 8, 2023 7:17 PM
> To: Wu, Jingjing
> Cc: dev@dpdk.org; Liu, Mingxia ; Xing, Beilei
> ; Zhang, Qi Z
> Subject: [PATCH v4 02/10] net/cpfl: introduce interface structure
>
> From: Beilei Xing
>
> Introduce cplf interf
> -static struct idpf_vport *
> +static struct cpfl_vport *
> cpfl_find_vport(struct cpfl_adapter_ext *adapter, uint32_t vport_id)
> {
> - struct idpf_vport *vport = NULL;
> + struct cpfl_vport *vport = NULL;
> int i;
>
> for (i = 0; i < adapter->cur_vport_nb; i++) {
> -
> -Original Message-
> From: Xing, Beilei
> Sent: Friday, September 8, 2023 7:17 PM
> To: Wu, Jingjing
> Cc: dev@dpdk.org; Liu, Mingxia ; Xing, Beilei
>
> Subject: [PATCH v4 08/10] net/cpfl: support vport list/info get
>
> From: Beilei Xing
>
> Support cp channel ops CPCHNL2_OP_CPF
> + /* warning if no match vport detected */
> + if (!matched)
> + PMD_INIT_LOG(WARNING, "No matched vport for
> representor %s "
> + "creation will be deferred when
> vport is detected",
> +
> -Original Message-
> From: Xing, Beilei
> Sent: Friday, September 8, 2023 7:17 PM
> To: Wu, Jingjing
> Cc: dev@dpdk.org; Liu, Mingxia ; Xing, Beilei
>
> Subject: [PATCH v4 10/10] net/cpfl: support link update for representor
>
> From: Beilei Xing
>
> Add link update ops for repre
On 2023-09-09 02:13, Konstantin Ananyev wrote:
06/09/2023 21:02, Mattias Rönnblom пишет:
On 2023-09-06 19:20, Stephen Hemminger wrote:
Move the random number state into thread local storage.
Me and Morten discussed TLS versus other alternatives in some other
thread. The downside of TLS that
85 matches
Mail list logo
