From: Gongming Chen
When the order of graph destroy is not the reverse order of create,
that is, when it is destroyed at will, the newly created graph id will
be the same as the existing graph id, which is not the expected unique
graph id. This graph id incorrectly corresponds to multiple graphs
From: Gongming Chen
When the order of graph destroy is not the reverse order of create,
that is, when it is destroyed at will, the newly created graph id will
be the same as the existing graph id, which is not the expected unique
graph id. This graph id incorrectly corresponds to multiple graphs
From: Gongming Chen
When the order of graph destroy is not the reverse order of create,
that is, when it is destroyed at will, the newly created graph id will
be the same as the existing graph id, which is not the expected unique
graph id. This graph id incorrectly corresponds to multiple graphs
From: Gongming Chen
When the order of graph destroy is not the reverse order of create,
that is, when it is destroyed at will, the newly created graph id will
be the same as the existing graph id, which is not the expected unique
graph id. This graph id incorrectly corresponds to multiple graphs
Hi Maxime and Chenbo,
Do you have any suggestions for how to address this?
Looking forward to hearing from you!
Thanks,
Gongming
> On Apr 3, 2024, at 11:52 PM, Gongming Chen
> wrote:
>
> Hi Maxime,
> Thanks for review.
>
>> On Apr 3, 2024, at 5:39 PM, Maxime Coquel
From: Gongming Chen
When a vhost user message handling error in the event dispatch thread,
vsocket reconn is added to the reconnection list of the reconnection
thread.
Since the reconnection, event dispatching and app configuration thread
do not have common thread protection restrictions, the
From: Gongming Chen
When a vhost user message handling error in the event dispatch thread,
vsocket reconn is added to the reconnection list of the reconnection
thread.
Since the reconnection, event dispatching and app configuration thread
do not have common thread protection restrictions, the
From: Gongming Chen
When a vhost user message handling error in the event dispatch thread,
vsocket reconn is added to the reconnection list of the reconnection
thread.
Since the reconnection, event dispatching and app configuration thread
do not have common thread protection restrictions, the
> On Jul 2, 2024, at 3:48 PM, Maxime Coquelin
> wrote:
>
> Hi Gongming,
>
> On 5/10/24 09:28, Gongming Chen wrote:
>> Hi Maxime and Chenbo,
>> Do you have any suggestions for how to address this?
>> Looking forward to hearing from you!
>
> Could y
0x03ed7ca0 in vhost_user_read_cb at lib/vhost/socket.c:330
#2 0x03ed625f in fdset_event_dispatch at lib/vhost/fd_man.c:283
Fixes: e623e0c6d8a5 ("vhost: add vhost-user client mode")
Cc: sta...@dpdk.org
Signed-off-by: Gongming Chen
---
lib/vhost/fd_man.c | 3 +++
From: Gongming Chen
When a vhost user message handling error in the event dispatch thread,
vsocket reconn is added to the reconnection list of the reconnection
thread.
Since the reconnection, event dispatching and app configuration thread
do not have common thread protection restrictions, the
From: Gongming Chen
When a vhost user message handling error in the event dispatch thread,
vsocket reconn is added to the reconnection list of the reconnection
thread.
Since the reconnection, event dispatching and app configuration thread
do not have common thread protection restrictions, the
From: Gongming Chen
When a vhost user message handling error in the event dispatch thread,
vsocket reconn is added to the reconnection list of the reconnection
thread.
Since the reconnection, event dispatching and app configuration thread
do not have common thread protection restrictions, the
re may be more
resources like vsocket, this thread lock can also be used to ensure
that resources are safely released after complete cleanup.
In this way, the threads will be clearer, and the complicated try lock
method is no longer needed.
Thanks,
Gongming
> On 4/3/24 08:31, Gongming Chen wr
From: Gongming Chen
When a vhost user message handling error in the event dispatch thread,
vsocket reconn is added to the reconnection list of the reconnection
thread.
Since the reconnection, event dispatching and app configuration thread
do not have common thread protection restrictions, the
15 matches
Mail list logo
