Re: Intel XEON Phi: Linux only?

Konstantin Belousov <[email protected]>
Newsgroups gmane.os.freebsd.current,gmane.os.freebsd.performance
Message-ID <[email protected]>
On Tue, Jun 19, 2012 at 09:51:35PM -0600, Scott Long wrote:
> On Jun 19, 2012, at 4:31 PM, Adrian Chadd wrote:
> 
> > I bet the answer is something like "Get FreeBSD up on it or work with
> > someone who can help you do that."
> > 
> > It's a catch-22 just like GPU - unless ${COMPANY} has customers using
> > it, they're not likely to dedicate resources, and no users will use it
> > if it doesn't work, so .. who will break the cycle. :)
> > 
> > 
> 
> If I may be blunt here, there's no point in idle speculation when
> there are several FreeBSD committers who work for Intel and write Intel
> drivers for FreeBSD. Let's ask them!

Intel released a documentation set for MIC, which does not even contain
any references to the startup sequence and system management. The only
thing which is provided is patch for Linux kernel.

I will be very delighted and want to appear completely wrong, but my
suspect is that FreeBSD will be in the same position with MIC as it is
with Intel GPUs. I asked Intel representative about MIC programming
documentation some time ago, the answer was 'we do provide extensive
documentation for SDK'. After I noted that this is not what is needed
to support the hardware on !Linux, I only get a blank eye.
signature.asc (application/pgp-signature, 196 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (FreeBSD)

iEYEARECAAYFAk/hl04ACgkQC3+MBN1Mb4iCGACfauJDOa/A8vS8RDWB+yjYVgZa
lO8An0L/vEGPYjix1K4W56ExS/TZa2Hm
=I/GG
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.