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.

Sign up for GitHub

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

Jump to bottom

SET commands #9

Open
CosmicSpaceGoose opened this issue Jul 8, 2023 · 4 comments
Open

SET commands #9

CosmicSpaceGoose opened this issue Jul 8, 2023 · 4 comments

Comments

@CosmicSpaceGoose
Copy link

Hi,

Why this crate implement GET commands only and not SET?
@cathay4t
Copy link
Member

My use case only require GET, but I think it should be simple to have SET support. Which part of ethtool you need for SET?

@CosmicSpaceGoose
Copy link
Author

In particular - rings and channels (#8). But for consistence, all currently implemented GET commands.

@SteamedFish
Copy link

I also needs SET for rings and channels, I'm currently working on it. The default value of rings and channels are not optimized for far speed ethernet cards, especially for 10GbE ethernet cards or more.

In particular - rings and channels (#8). But for consistence, all currently implemented GET commands.

@SteamedFish
Copy link

In particular - rings and channels (#8). But for consistence, all currently implemented GET commands.

I found many issues with the netlink interface of ethtool, especially on virtual machines. Sometimes I cannot even get. I've switched to ioctl interface.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@SteamedFish @cathay4t @CosmicSpaceGoose