You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On DPDK documentation it is mentioned that --file-prefix could be used to start processes that don't want to cooperate with same memory regions. The parsing of the flag was added in this commit to F-Stack.
Could you please provide an example about how this flag should be used to start two independent F-Stack applications and if something additional should be configured in order to make it work?
In my experiment, I tried starting two independent clients that use the F-Stack API to interact with a HTTP Server. When the second client starts, the first client hangs and the connection to the server is terminated. The configuration is the following:
This is the diff (from default config.ini) of configurations I used:
you looks like new to dpdk, dpdk only allow one primary process on one pc, and proc-id means the program's index, you can take it as like dpdk process sequence num, one lcore is only allowed on one cpu core.
try the second process with --proc-type=secondary --proc-id=1
by the way, you should set the lcore_mask=0x3 in config file(0011 in binary,means the first and second cpu core will bind with dpdk lcore)
On DPDK documentation it is mentioned that
--file-prefix
could be used to start processes that don't want to cooperate with same memory regions. The parsing of the flag was added in this commit to F-Stack.Could you please provide an example about how this flag should be used to start two independent F-Stack applications and if something additional should be configured in order to make it work?
In my experiment, I tried starting two independent clients that use the F-Stack API to interact with a HTTP Server. When the second client starts, the first client hangs and the connection to the server is terminated. The configuration is the following:
This is the diff (from default
config.ini
) of configurations I used:For client 1:
For client 2:
I started the clients with the following commands:
The text was updated successfully, but these errors were encountered: