Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running multiple independent F-Stack applications #836

Open
RaduNichita opened this issue Aug 15, 2024 · 1 comment
Open

Running multiple independent F-Stack applications #836

RaduNichita opened this issue Aug 15, 2024 · 1 comment

Comments

@RaduNichita
Copy link

RaduNichita commented Aug 15, 2024

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:

< lcore_mask=2
---
> lcore_mask=1
15,17d14
< file_prefix=app1
39c36
< pkt_tx_delay=0
---
> pkt_tx_delay=100
77c74
< log_level=5
---
> # log_level=0

For client 2:

< file_prefix=app2
38c36
< pkt_tx_delay=0
---
> pkt_tx_delay=100
76c74
< log_level=5
---
> # log_level=0

I started the clients with the following commands:

./client --conf ../config_app1.ini --proc-type=primary --proc-id=0
./client --conf ../config_app2.ini --proc-type=primary --proc-id=0
@hei1046035362
Copy link

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants