ANDROID: GKI: Add memcg ABI padding

To facilitate nonspecific potential future backports and fixes.

These structures are allocated from dedicated slabs [1], so there is no
risk of incurring significant memory overhead as a result of these
additions.

[1] https://r.android.com/3623495

Bug: 417480479
Change-Id: I4b1bdbf4edcb857fdf66407d54e8721674e26de4
Signed-off-by: T.J. Mercier <tjmercier@google.com>
This commit is contained in:
T.J. Mercier
2025-05-13 17:38:29 +00:00
committed by Carlos Llamas
parent d48d0d0892
commit 060da33ae4

View File

@@ -10,6 +10,7 @@
#ifndef _LINUX_MEMCONTROL_H
#define _LINUX_MEMCONTROL_H
#include <linux/android_kabi.h>
#include <linux/cgroup.h>
#include <linux/vm_event_item.h>
#include <linux/hardirq.h>
@@ -113,6 +114,8 @@ struct mem_cgroup_per_node {
CACHELINE_PADDING(_pad2_);
unsigned long lru_zone_size[MAX_NR_ZONES][NR_LRU_LISTS];
struct mem_cgroup_reclaim_iter iter;
ANDROID_BACKPORT_RESERVE(1);
};
struct mem_cgroup_threshold {
@@ -323,6 +326,7 @@ struct mem_cgroup {
spinlock_t event_list_lock;
#endif /* CONFIG_MEMCG_V1 */
ANDROID_BACKPORT_RESERVE(1);
ANDROID_OEM_DATA_ARRAY(1, 2);
struct mem_cgroup_per_node *nodeinfo[];