hpc documentation - technical:gridengine:geco

01_background

anonymous@undisclosed.example.com (Anonymous) — Mon, 04 Jan 2016 20:35:40 +0000

Better Integration with Grid Engine Our first attempts at augmenting Grid Engine with our own CGroup support exploited the same process-creation notification mechanism that Linux's cgred (CGroups Rules Engine Daemon) uses to quarantine new processes. When a process forks, executes a program, or exits, the kernel will deliver information about that process to userland programs that are listening for such notifications via a netlink interface. A daemon can examine the information and…

02_library

anonymous@undisclosed.example.com (Anonymous) — Mon, 04 Jan 2016 21:02:59 +0000

GECO Core Library At the core of GECO is a shared library containing APIs used to: * Create and manage per-job CGroup containers * Manage GECO state information for running jobs * Load, serialize, and deserialize per-job granted resource information (e.g. core counts, memory limits, coprocessor hardware)

03_geco-rsrcinfo

anonymous@undisclosed.example.com (Anonymous) — Tue, 22 Dec 2015 18:16:25 +0000

The geco-rsrcinfo Command The geco-rsrcinfo command makes use of the job resource lookup functionality in the GECO core library to: * parse the output of qstat -xml -j #.# (either provided on stdin or executed by geco-rsrcinfo itself)

04_gecod

anonymous@undisclosed.example.com (Anonymous) — Thu, 07 Jan 2016 21:26:52 +0000

gecod The Grid Engine Cgroup Orchestrator Daemon (gecod) is responsible for: * The creation and management of per-job cgroups on a node * The addition of processes to per-job cgroups at the request of the patched exec() funtions (quarantine) *

start

anonymous@undisclosed.example.com (Anonymous) — Fri, 15 Jan 2016 15:38:28 +0000

Full Support for Linux CGroups Using GECO Several variants of Grid Engine claim to support integration with Linux CGroups to control resource allocations. One such variant was chosen for the University's Farber cluster partly for the sake of this feature. We were incredibly disappointed to eventually figure out for ourselves that the marketing hype was true in a very rudimentary sense. Some of the issues we elucidated were: