From: Andrea Arcangeli <aarcange@redhat.com>
To: Shaohua Li <shaohua.li@intel.com>
Cc: David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch 1/5]thp: improve the error code path
Date: Thu, 10 Nov 2011 15:14:12 +0100 [thread overview]
Message-ID: <20111110141412.GW5075@redhat.com> (raw)
In-Reply-To: <1320904609.22361.239.camel@sli10-conroe>
On Thu, Nov 10, 2011 at 01:56:49PM +0800, Shaohua Li wrote:
> +static struct kobject *hugepage_kobj;
It's minor nitpick but we don't need to put this in .bss, passing it
as hugepage_init_sysfs(struct kobject **hugepage_kobj) and storing it
there in case the error returned by hugepage_init_sysfs is zero should
be fine. The feature cannot be unloaded so we can lose the pointer
after init is complete.
Then I think we can be done with this... and it looks better now.
> +static int __init hugepage_init_sysfs(void)
> {
> int err;
> -#ifdef CONFIG_SYSFS
> - static struct kobject *hugepage_kobj;
> -#endif
>
> - err = -EINVAL;
> - if (!has_transparent_hugepage()) {
> - transparent_hugepage_flags = 0;
> - goto out;
> - }
> -
> -#ifdef CONFIG_SYSFS
> - err = -ENOMEM;
> hugepage_kobj = kobject_create_and_add("transparent_hugepage", mm_kobj);
> if (unlikely(!hugepage_kobj)) {
> printk(KERN_ERR "hugepage: failed kobject create\n");
> - goto out;
> + return -ENOMEM;
> }
>
> err = sysfs_create_group(hugepage_kobj, &hugepage_attr_group);
> if (err) {
> printk(KERN_ERR "hugepage: failed register hugeage group\n");
> - goto out;
> + goto delete_obj;
> }
>
> err = sysfs_create_group(hugepage_kobj, &khugepaged_attr_group);
> if (err) {
> printk(KERN_ERR "hugepage: failed register hugeage group\n");
> - goto out;
> + goto remove_hp_group;
> }
> -#endif
> +
> + return 0;
> +
> +remove_hp_group:
> + sysfs_remove_group(hugepage_kobj, &hugepage_attr_group);
> +delete_obj:
> + kobject_put(hugepage_kobj);
> + return err;
> +}
> +
> +static void __init hugepage_exit_sysfs(void)
> +{
> + sysfs_remove_group(hugepage_kobj, &khugepaged_attr_group);
> + sysfs_remove_group(hugepage_kobj, &hugepage_attr_group);
> + kobject_put(hugepage_kobj);
> +}
> +#else
> +static inline int hugepage_init_sysfs(void)
> +{
> + return 0;
> +}
> +
> +static inline void hugepage_exit_sysfs(void)
> +{
> +}
> +#endif /* CONFIG_SYSFS */
> +
> +static int __init hugepage_init(void)
> +{
> + int err;
struct kobject *hugepage_kobj;
> +
> + if (!has_transparent_hugepage()) {
> + transparent_hugepage_flags = 0;
> + return -EINVAL;
> + }
> +
> + err = hugepage_init_sysfs();
err = hugepage_init_sysfs(&hugepage_kobj);
> + if (err)
> + return err;
>
> err = khugepaged_slab_init();
> if (err)
> @@ -545,7 +572,9 @@ static int __init hugepage_init(void)
>
> set_recommended_min_free_kbytes();
>
> + return 0;
> out:
> + hugepage_exit_sysfs();
hugepage_exit_sysfs(hugepage_kobj);
> return err;
> }
> module_init(hugepage_init)
>
>
--
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>
next prev parent reply other threads:[~2011-11-10 14:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 2:58 [patch 1/5]thp: improve the error code path Shaohua Li
2011-10-25 11:44 ` Andrea Arcangeli
2011-10-26 1:48 ` Shaohua Li
2011-11-07 5:17 ` Shaohua Li
2011-11-10 2:18 ` Andrea Arcangeli
2011-11-10 2:33 ` Shaohua Li
2011-11-10 2:43 ` David Rientjes
2011-11-10 3:06 ` Andrea Arcangeli
2011-11-10 4:43 ` David Rientjes
2011-11-10 5:56 ` Shaohua Li
2011-11-10 6:08 ` David Rientjes
2011-11-10 6:27 ` Shaohua Li
2011-11-10 14:14 ` Andrea Arcangeli [this message]
2011-11-11 6:33 ` Shaohua Li
2011-11-11 6:50 ` Andrea Arcangeli
2011-11-10 2:59 ` Andrea Arcangeli
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=20111110141412.GW5075@redhat.com \
--to=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=shaohua.li@intel.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;
as well as URLs for NNTP newsgroup(s).