# Reserving cores for GPU jobs

**URL:** https://community.openpbs.org/t/reserving-cores-for-gpu-jobs/2951
**Category:** Users/Site Administrators
**Created:** [January 28, 2022, 3:48pm UTC](https://community.openpbs.org/t/reserving-cores-for-gpu-jobs/2951 "2022-01-28T15:48:55Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![weallcock](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.openpbs.org/weallcock/32/466_2.png) [@weallcock](https://community.openpbs.org/u/weallcock)
#### Post date: [January 30, 2022, 12:12am UTC](https://community.openpbs.org/t/reserving-cores-for-gpu-jobs/2951/2 "2022-01-30T00:12:12Z")

</div>

Take a look at my reply [here](https://community.openpbs.org/t/multiple-cgroups-per-vnode-realistic-use-cases/2931/2). Depending on your processor, if it has multiple NUMA nodes, you might be able to configure PBS cgroups for “vnode per NUMA node” and end up with something along the lines you want. There are lots of reasons it might not work (you might only have one NUMA node, both GPUs could be on one NUMA node which is probably not what you want, etc) but you might get something useful using available configuration. Hope that helps.

---

_[View the full topic](https://community.openpbs.org/t/reserving-cores-for-gpu-jobs/2951)._
