Thanks all for your repliy, But what I need is to stop user to use --mem and --mem-per-cpu , but I can't figure out this with cgroup and tres. How can I use the "submit filter", should I modify the source code of SLURM? Is there any way to config some files of SLURM to solve this problem? All the best, Ashlee
2017-11-03 5:17 GMT+08:00 E.S. Rosenberg <esr+slurm-...@mail.hebrew.edu>: > If a user has a program that is strictly single threaded but does need the > full (or close to) full amount of memory available should you be preventing > them from running? > I guess an argument can be made that this will encourage them to figure > out how to re-do their program multi-threaded but this may just not be what > you want to accomplish... > (also another user may have a program with a /really/ small memory > footprint that can still run on the node....) > > Just a point for thought... > All the best, > Eli > > On Thu, Nov 2, 2017 at 1:53 PM, Rajiv Nishtala <nishtala....@gmail.com> > wrote: > >> >> It can also constrain the memory a CPU can use. for instance, using >> --mem-per-cpu ..I maybe wrong. >> >> Best, >> Rajiv >> >> >> >> On 02/11/17 11:36, Chris Samuel wrote: >> >>> On Thursday, 2 November 2017 8:02:47 PM AEDT Rajiv Nishtala wrote: >>> >>> And also using cgroups; https://slurm.schedmd.com/cgroup.conf.html >>>> >>> That will constrain the memory a job can use to what it has asked for, >>> but I >>> think that the original poster was asking how to stop a user asking for >>> that >>> much memory in the first place. >>> >>> The other option would be via a submit filter of course. >>> >>> cheers, >>> Chris >>> >> >
