Thread (62 messages) 62 messages, 11 authors, 2012-01-26

Re: [RFC 1/3] /dev/low_mem_notify

From: Arnd Bergmann <arnd@arndb.de>
Date: 2012-01-24 16:22:51
Also in: lkml

On Wednesday 18 January 2012, Pekka Enberg wrote:
quoted
quoted
+struct vmnotify_event {
+     /* Size of the struct for ABI extensibility. */
+     __u32                   size;
+
+     __u64                   nr_avail_pages;
+
+     __u64                   nr_swap_pages;
+
+     __u64                   nr_free_pages;
+};
Two fields here most likely session-constant, (nr_avail_pages and
nr_swap_pages), seems not much sense to report them in every event.  If we
have memory/swap hotplug user-space can use sysinfo() call.
I actually changed the ABI to look like this:

struct vmnotify_event {
        /*
         * Size of the struct for ABI extensibility.
         */
        __u32                   size;

        __u64                   attrs;

        __u64                   attr_values[];
};

So userspace can decide which fields to include in notifications.
Please make the first member a __u64 instead of a __u32. This will
avoid incompatibility between 32 and 64 bit processes, which have
different alignment rules on x86: x86-32 would implicitly pack the
struct while x86-64 would add padding with your layout.

	Arnd

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help