[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080223000606.d7474c91.akpm@linux-foundation.org>
Date: Sat, 23 Feb 2008 00:06:06 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org,
netdev@...r.kernel.org, trond.myklebust@....uio.no,
Alexey Dobriyan <adobriyan@...il.com>
Subject: Re: [PATCH 10/28] mm: memory reserve management
On Wed, 20 Feb 2008 15:46:20 +0100 Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:
> Generic reserve management code.
>
> It provides methods to reserve and charge. Upon this, generic alloc/free style
> reserve pools could be build, which could fully replace mempool_t
> functionality.
>
> It should also allow for a Banker's algorithm replacement of __GFP_NOFAIL.
Generally: the comments in this code are a bit straggly and hard to follow.
They'd be worth a revisit.
> +/*
> + * Simple output of the reserve tree in: /proc/reserve_info
> + * Example:
> + *
> + * localhost ~ # cat /proc/reserve_info
> + * total reserve 8156K (0/544817)
> + * total network reserve 8156K (0/544817)
> + * network TX reserve 196K (0/49)
> + * protocol TX pages 196K (0/49)
> + * network RX reserve 7960K (0/544768)
> + * IPv6 route cache 1372K (0/4096)
> + * IPv4 route cache 5468K (0/16384)
> + * SKB data reserve 1120K (0/524288)
> + * IPv6 fragment cache 560K (0/262144)
> + * IPv4 fragment cache 560K (0/262144)
> + */
Well, "Simple" was a freudian typo. Not designed for programmatic parsing,
I see.
> +static __init int mem_reserve_proc_init(void)
> +{
> + struct proc_dir_entry *entry;
> +
> + entry = create_proc_entry("reserve_info", S_IRUSR, NULL);
I think we're supposed to use proc_create(). Blame Alexey.
> + if (entry)
> + entry->proc_fops = &mem_reserve_opterations;
> +
> + return 0;
> +}
> +
> +__initcall(mem_reserve_proc_init);
module_init() is more trendy.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists