Stats

  • Locked Locked
  • Replies 1
  • Subscribers 62
  • Views 15062
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How to use the Encounter RTL Compiler Super-Thread with Tivoli Workload LoadLeveler

lvcargnini

Hello all,

 Please I would like to use my Encounter RTL Compiler, later the EDI, to place the parallel synthesis into a HPC cluster. I understand that for this purpose I must use Super-Thread, and that I must configure it using:

set_attribute super_thread_servers {machine_names} /

 In this stage I already have some issues, shouldn't I use only the keyword batch instead of the node machines ?

Second, I don't have and won't have rsh access to the nodes, and they use Tivoli workload to control the access and jobs launching into the HPC.

 If I understand well, I should use:

rc:/> set_attribute super_thread_batch_command  {llsubmit .....} /

rc:/> set_attribute super_thread_kill_command {llkill ....} / 

So how do I properly configure it for Tivoli queue commands.

Last how to set the number of CPUs ? using set_attribute ? command line there is something like -lsf_cpus 4, into tho attributes how to do that, instead of placing X times the machine or bactch into  super_thread_servers variable.

Best Regards,

Vitorio. 

 

  •  Hi Vitorio,

     I am not sure I see any reason why the commands you have wil not work for Tivoli.  The command line certainly does not support non-lsf optionsbut nothing prevents you from using -e and creating any variable that suits your needs:

    rc -e 'set tivoli_queue fast; set tivoli_num_cpus 4; set tivoli_options....; ' . . .

     I am not familiar with Tivoli but would need more information on scenarios that do not work.The command provided are fairly general so should suffice. Please file an SR if they do not

     gh-

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.