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

Using EAL Parameters #80

Open
KirklandWireless opened this issue Aug 18, 2017 · 1 comment
Open

Using EAL Parameters #80

KirklandWireless opened this issue Aug 18, 2017 · 1 comment
Assignees

Comments

@KirklandWireless
Copy link

Hi

I wanted to know if it is possible to use dpdk's EAL arguments with these functions. For example I want to use --socket-mem ,-b (blacklist ports), -n (memory channels), and --xen-dom0. I experimented a little bit but couldn't find anything. I think the -f 'config' command does not allow for these parameters either correct?

@apanda
Copy link
Member

apanda commented Sep 7, 2017

Hi
Some of these you can control already:

  • --socket-mem is the same as pool_size

  • -b we implicitly blacklist any port that is not explicitly specified either in the config file or in a commandline parameter to the program.

The rest are currently not, in particular -n is currently hardcoded to 4 (https://github.com/NetSys/NetBricks/blob/master/native/init.c#L126) and I have never used xen-dom0 and hence have no support for it. If you want to extend config_reader.rs and init.c I'd be happy to incorporate configuration for this I'd be happy to incorporate that. I can also try and push a change incorporating this later if it is being problematic, just let me know.

Thanks for using NetBricks, and sorry for the delay in getting back to you.

@apanda apanda self-assigned this Sep 7, 2017
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