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

confirm k1om support via test #73

Open
ghost opened this issue Nov 7, 2017 · 2 comments
Open

confirm k1om support via test #73

ghost opened this issue Nov 7, 2017 · 2 comments

Comments

@ghost
Copy link

ghost commented Nov 7, 2017

greetings @edanor
Please consider implementation of benchmark test of non-vector code vs fully optimized code for k1om.
k1om is flooding market, we need to see (in seconds) how this library rocks! [I already know from usage].

Thanks,
coast

@edanor
Copy link
Owner

edanor commented Nov 16, 2017

Hi,

I'm glad that you find this library useful! Hope it works well for you.

Unfortunately the reason why KNC is flooding market is that it has been EOL'ed ( see: https://ark.intel.com/products/series/92649/Intel-Xeon-Phi-x100-Product-Family ). This is the reason why computer centers are getting rid of it.

Because of AVX512 already released, the whole k1om ISA is unlikely to re-appear. In other words: making any code developments in that direction will only create a long term burden on the library. Because the library only covers code generation, you will still have to work hard on your code to make sure it works on KNC. For instance all loads have to be aligned or else you would pay a HUGE performance penalty. So even if it is cheap hardware, long term you might save some money (and a lot of time) on software development if you choose AVX512 machine or CUDA-enabled coprocessor.

Another, more practical problems are that I don't have the access to hardware to verify whether the code works as expected and I would have to spend my private time on developing this code, which I personally don't need (I mean the benchmarks + KNC plugin, not the whole library;]).

Since this is a free software you have two choices:

  1. write the code on your own and submit a pull request. I am more than willing to review and accept most of modifications and guide you through the development process if needed.
  2. make a donation so that I can pay somebody competent for making this modification for you. Send me a message at [email protected] if you are interested so that we can discuss any details.

Cheers,
Przemek.

@ghost
Copy link
Author

ghost commented Dec 11, 2017 via email

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

1 participant