From: Christoph Hellwig <hch@infradead.org>
To: Vladimir Saveliev <vs@namesys.com>
Cc: linux-mm <linux-mm@kvack.org>, Andrew Morton <akpm@osdl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] per thread page reservation patch
Date: Fri, 7 Jan 2005 19:05:45 +0000 [thread overview]
Message-ID: <20050107190545.GA13898@infradead.org> (raw)
In-Reply-To: <1105118217.3616.171.camel@tribesman.namesys.com>
> diff -puN include/linux/gfp.h~reiser4-perthread-pages include/linux/gfp.h
> --- linux-2.6.10-rc3/include/linux/gfp.h~reiser4-perthread-pages 2004-12-22 20:09:44.153164276 +0300
> +++ linux-2.6.10-rc3-vs/include/linux/gfp.h 2004-12-22 20:09:44.199167794 +0300
> @@ -134,4 +134,8 @@ extern void FASTCALL(free_cold_page(stru
>
> void page_alloc_init(void);
>
> +int perthread_pages_reserve(int nrpages, int gfp);
> +void perthread_pages_release(int nrpages);
> +int perthread_pages_count(void);
> +
> #endif /* __LINUX_GFP_H */
> diff -puN include/linux/init_task.h~reiser4-perthread-pages include/linux/init_task.h
> --- linux-2.6.10-rc3/include/linux/init_task.h~reiser4-perthread-pages 2004-12-22 20:09:44.160164812 +0300
> +++ linux-2.6.10-rc3-vs/include/linux/init_task.h 2004-12-22 20:09:44.201167947 +0300
> @@ -112,8 +112,8 @@ extern struct group_info init_groups;
> .proc_lock = SPIN_LOCK_UNLOCKED, \
> .switch_lock = SPIN_LOCK_UNLOCKED, \
> .journal_info = NULL, \
> + .private_pages = LIST_HEAD_INIT(tsk.private_pages), \
> + .private_pages_count = 0, \
> }
>
> -
> -
> #endif
> diff -puN include/linux/sched.h~reiser4-perthread-pages include/linux/sched.h
> --- linux-2.6.10-rc3/include/linux/sched.h~reiser4-perthread-pages 2004-12-22 20:09:44.170165576 +0300
> +++ linux-2.6.10-rc3-vs/include/linux/sched.h 2004-12-22 20:09:44.204168176 +0300
> @@ -691,6 +691,9 @@ struct task_struct {
> nodemask_t mems_allowed;
> int cpuset_mems_generation;
> #endif
> +
> + struct list_head private_pages; /* per-process private pages */
> + int private_pages_count;
> };
>
> static inline pid_t process_group(struct task_struct *tsk)
> diff -puN kernel/fork.c~reiser4-perthread-pages kernel/fork.c
> --- linux-2.6.10-rc3/kernel/fork.c~reiser4-perthread-pages 2004-12-22 20:09:44.179166264 +0300
> +++ linux-2.6.10-rc3-vs/kernel/fork.c 2004-12-22 20:09:44.215169017 +0300
> @@ -154,6 +154,10 @@ static struct task_struct *dup_task_stru
> tsk->thread_info = ti;
> ti->task = tsk;
>
> + /* initialize list of pages privately reserved by process */
> + INIT_LIST_HEAD(&tsk->private_pages);
> + tsk->private_pages_count = 0;
> +
> /* One for us, one for whoever does the "release_task()" (usually parent) */
> atomic_set(&tsk->usage,2);
> return tsk;
> diff -puN mm/page_alloc.c~reiser4-perthread-pages mm/page_alloc.c
> --- linux-2.6.10-rc3/mm/page_alloc.c~reiser4-perthread-pages 2004-12-22 20:09:44.187166876 +0300
> +++ linux-2.6.10-rc3-vs/mm/page_alloc.c 2004-12-22 20:09:44.219169323 +0300
> @@ -551,6 +551,97 @@ void fastcall free_cold_page(struct page
> free_hot_cold_page(page, 1);
> }
>
> +static inline struct list_head *get_per_thread_pages(void)
> +{
> + return ¤t->private_pages;
> +}
this is a completely useless wrapper that doesn't buy anything.
> +int perthread_pages_reserve(int nrpages, int gfp)
> +{
> + int i;
> + struct list_head accumulator;
> + struct list_head *per_thread;
> +
> + per_thread = get_per_thread_pages();
> + INIT_LIST_HEAD(&accumulator);
> + list_splice_init(per_thread, &accumulator);
Can probably be written much simpler as:
int perthread_pages_reserve(int nrpages, int gfp)
{
LIST_HEAD(accumulator);
int i;
list_splice_init(¤t->private_pages, &accumulator);
Now the big question is, what's synchronizing access to
current->private_pages?
> + for (i = 0; i < nrpages; ++i) {
> + struct page *page;
> +
> + page = alloc_page(gfp);
> + if (page != NULL)
> + list_add(&page->lru, &accumulator);
> + else {
> + for (; i > 0; --i) {
> + page = list_entry(accumulator.next, struct page, lru);
> + list_del(&page->lru);
> + page_cache_release(page);
> + }
> + return -ENOMEM;
> + }
> + }
Would be much more readable with the error condition handling at the
end of the function and a goto.
> +int perthread_pages_count(void)
> +{
> + return current->private_pages_count;
> +}
> +EXPORT_SYMBOL(perthread_pages_count);
Again a completely useless wrapper.
> +static inline struct page *
> +perthread_pages_alloc(void)
> +{
> + struct list_head *perthread_pages;
> +
> + /*
> + * try to allocate pages from the per-thread private_pages pool. No
> + * locking is needed: this list can only be modified by the thread
> + * itself, and not by interrupts or other threads.
> + */
> + perthread_pages = get_per_thread_pages();
> + if (!in_interrupt() && !list_empty(perthread_pages)) {
> + struct page *page;
> +
> + page = list_entry(perthread_pages->next, struct page, lru);
> + list_del(&page->lru);
> + current->private_pages_count--;
> + /*
> + * per-thread page is already initialized, just return it.
> + */
> + return page;
> + } else
> + return NULL;
> +}
Would be written much cleaner with a single return statement and the
comment above the function, ala:
/*
* try to allocate pages from the per-thread private_pages pool. No
* locking is needed: this list can only be modified by the thread
* itself, and not by interrupts or other threads.
*/
static inline struct page *perthread_pages_alloc(void)
{
struct list_head *perthread_pages = ¤t->private_pages;
struct page *page = NULL;
if (!in_interrupt() && !list_empty(perthread_pages)) {
page = list_entry(perthread_pages->next, struct page, lru);
list_del(&page->lru);
current->private_pages_count--;
}
return page;
}
> + if (order == 0) {
> + page = perthread_pages_alloc();
> + if (page != NULL)
> + return page;
> + }
> +
You should at least move the !in_interrupt() condition out here.
--
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/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-01-07 19:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050103011113.6f6c8f44.akpm@osdl.org>
[not found] ` <20050103114854.GA18408@infradead.org>
[not found] ` <41DC2386.9010701@namesys.com>
[not found] ` <1105019521.7074.79.camel@tribesman.namesys.com>
[not found] ` <20050107144644.GA9606@infradead.org>
2005-01-07 17:16 ` Vladimir Saveliev
2005-01-07 18:48 ` Andrew Morton
2005-01-07 20:21 ` Nikita Danilov
2005-01-07 19:05 ` Christoph Hellwig [this message]
2005-01-07 19:12 ` Christoph Hellwig
2005-01-07 19:21 ` Robert Love
2005-01-07 20:48 ` Nikita Danilov
2005-01-07 20:54 ` Christoph Hellwig
2005-01-07 21:00 ` Nikita Danilov
2005-01-07 21:07 ` Christoph Hellwig
2005-01-07 19:14 ` Paulo Marques
2005-01-07 19:32 ` Christoph Hellwig
2005-01-07 19:42 ` Andi Kleen
2005-01-07 20:55 ` Nikita Danilov
2005-01-07 21:24 ` Andrew Morton
2005-01-07 21:24 ` Andi Kleen
2005-01-07 22:12 ` Nikita Danilov
2005-01-07 23:03 ` Andrew Morton
2005-01-07 23:17 ` Nikita Danilov
2005-01-07 23:43 ` Andrew Morton
2005-01-08 12:44 ` Nikita Danilov
2005-01-08 13:43 ` Hugh Dickins
2005-01-09 11:35 ` Marcelo Tosatti
2005-01-09 18:16 ` Nikita Danilov
2005-01-25 16:39 ` reiser4 core patches: [Was: [RFC] per thread page reservation patch] Vladimir Saveliev
2005-01-27 10:37 ` Adrian Bunk
2005-01-27 11:01 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050107190545.GA13898@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vs@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox