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

Current version of netperf does not contain ppc64le support #1412

Open
bssrikanth opened this issue Jun 6, 2018 · 8 comments
Open

Current version of netperf does not contain ppc64le support #1412

bssrikanth opened this issue Jun 6, 2018 · 8 comments

Comments

@bssrikanth
Copy link
Contributor

config.guess of either netperf-2.4.5 or netperf-2.6.0 does not include support for ppc64le. I see PR for same in netperf github @ HewlettPackard/netperf#6 .. but same is not updated in tp-qemu.

@bssrikanth
Copy link
Contributor Author

@ldoktor is it ok if I create PR with updated netperf with changes to all locations in testcases cfg to point to new version of it?

@ldoktor
Copy link
Member

ldoktor commented Jun 20, 2018

That would be welcome, thank you for noticing this 😄

@bssrikanth
Copy link
Contributor Author

@ldoktor I have come across more generic approach for handling stress in utils_test [VMStress]. Which is better than having individual stress's in deps within avocado -> coyping to dest -> setup. I am in process of implementing this approach for netperf stress on ppc64le.
Closing this issue.

@ldoktor
Copy link
Member

ldoktor commented Jun 20, 2018

OK, would you care to share some details when it's ready? :-) Also fixing nerperf might be good for the community so let me take that over...

@bssrikanth
Copy link
Contributor Author

@ldoktor I am using recently added libraries @ avocado-vt/pull/1467.. I had sent uperf stress scenarios using same in tp-libvirt/pull/1680 .. For now I am implementing same approach in kdump_with_stress script for running netperf on ppc64le.. same can be reused as well for other archs..

@bssrikanth
Copy link
Contributor Author

I thought we can now start using generic apis to download/clone stress tools from hosted environment directly to place where it is required to run.

If you are thinking that having the updated stress package to be part of deps would help, then I will pursue this issue and send the PR.

@bssrikanth bssrikanth reopened this Jun 20, 2018
@ldoktor
Copy link
Member

ldoktor commented Jun 20, 2018

Well hard to say. I prefer fetching from upstream, but this was changed quite recently in 11975c3 to download from our git (probably to save bandwidth and avoid external links?

@ldoktor
Copy link
Member

ldoktor commented Jun 20, 2018

OK, I tried fixing it, but netperf test is in such a terrible state that I can't actually get to run it (last time I ran it was about a year ago and since then there are so many changes that effectively broke it for me). So if you want to fix it, good. If someone else want to fix it, good. But I give up. (the biggest changes that broke it for me are: a46ec52 and 88d5084

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