Gilles, thank you for the information. Just to confirm that I understand
correctly, the vendor-supplied a replacement/substitute for syscfg. You
then wrote a slurm plugin for it that used the vendor-supplied tool.

On Sat, Apr 1, 2017 at 11:58 PM, <gil...@rist.or.jp> wrote:

>  Kenneth,
>
>
>
> i cannot tell whether syscfg works with Supermicro KNL boards or not, and
> i guess you just have to try
>
> (you can refer to the source code of the knl_generic plugin to figure out
> which commands are issued)
>
>
>
> i installed slurm on a KNL cluster from an other vendor on which syscfg
> cannot be used to
>
> query/set the memory/cluster mode, and here is what i found
>
> - the knl_generic plugin can be used "as is" as long as you have an
> utility that can
>
> individually query/set the cluster/memory mode : you simply need to write
> your own wrapper
>
> and point knl_generic.conf to it
>
> - in my case, cluster and memory mode must be set all at once, so it was
> not possible to write a wrapper
>
> - i ended up duplicating the knl_generic plugin
>
>   * i use /var/run/hwloc/knl_memoryside_cache to query the cluster and
> memory mode (this file is generated by xppssl-hwloc-sbin package)
>
>   * a wrapper is invoked to set memory *and* cluster mode all at once
>
>   * i removed some logic used to build the command line and parse the
> output of the intel syscfg command
>
> imho, the knl_generic plugin could be revamped to be more generic by
> wrapping the intel syscfg into a script that
>
> *atomically* query/set cluster and memory mode,with an easily parsable
> command line and output format
>
>
>
> i hope this helps
>
>
>
> Gilles
>
> ----- Original Message -----
>
> Does slurm also work well with Supermicro KNL boards, such as
>
> https://www.supermicro.com/products/system/2U/5028/SYS-5028TK-HTR.cfm
>
> My understanding is that slurm uses syscfg, provided by Intel, to
> configure a KNL node:
>
> https://slurm.schedmd.com/intel_knl.html
>
> I'm not sure if syscfg works on those boards, and whether or not slurm has
> a workaround if it doesn't.
>
>

Reply via email to