Dear Team, Thank you for providing input. Then share the steps to represent the MICs and the prolog manipulates lock files to assign specific MICs to the job when it starts.
In our setup we are having 4 servers with 2 mic installed on each server. Thank You Atul Yadav ---------- Forwarded message ---------- From: William Hay <w....@ucl.ac.uk> Date: Thu, Jul 24, 2014 at 1:23 PM Subject: Re: [gridengine users] Intel MIC integration with scheduler To: users@gridengine.org On Wed, 23 Jul 2014 17:18:09 +0000 Atul Yadav <atulyadavt...@gmail.com> wrote: > Dear Team, > > We are planning to use gridengine scheduler for managing Intel MIC > resources. > > We need your assistance building GE2011.11p1 with Intel MIC. > > Please share the steps for completing the activity. I'm not sure there is such a thing as "the steps". We have several machines with two MICs each and are still using an older version of Grid Engine. We treat them as coprocessors. We have a complex defined to represent the MICs and the prolog manipulates lock files to assign specific MICs to the job when it starts. We then drop a file listing the MIC to use in the job's TMPDIR in a similar fashion to the way parallel environments create a machines file. At the moment we don't enforce the allocation but rely on the honor system. An alternative to treating them as coprocessors would be to treat them as execution hosts in their own right. Compile Grid Engine for the MIC and run an execd on them(warning I've never tried this). If you wanted to use them as a co-processor in this scenario you could then define PEs with a single slot on the host and the remaining slots on the MICs. Use -masterq to ensure the job starts on the host with SLAVE slots on the MICs. William _______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
signature.asc
Description: PGP signature
_______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
