All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Aravamudan <nacc@us.ibm.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, Greg KH <gregkh@suse.de>
Subject: Re: [patch 05/21] hugetlb: new sysfs interface
Date: Tue, 1 Jul 2008 17:24:31 -0700	[thread overview]
Message-ID: <20080702002431.GA24625@us.ibm.com> (raw)
In-Reply-To: <20080612011149.GA21542@us.ibm.com>

On 11.06.2008 [19:11:49 -0600], Nishanth Aravamudan wrote:
> On 10.06.2008 [05:02:34 +0200], Nick Piggin wrote:
> > On Sun, Jun 08, 2008 at 11:59:41AM -0700, Andrew Morton wrote:
> > > On Wed, 04 Jun 2008 21:29:44 +1000 npiggin@suse.de wrote:
> > > 
> > > > Provide new hugepages user APIs that are more suited to multiple hstates in
> > > > sysfs. There is a new directory, /sys/kernel/hugepages. Underneath that
> > > > directory there will be a directory per-supported hugepage size, e.g.:
> > > > 
> > > > /sys/kernel/hugepages/hugepages-64kB
> > > > /sys/kernel/hugepages/hugepages-16384kB
> > > > /sys/kernel/hugepages/hugepages-16777216kB
> > > 
> > > Maybe /sys/mm or /sys/vm would be a more appropriate place.
> > 
> > I'm thinking all the random kernel subsystems under /sys/ should
> > rather be moved to /sys/kernel/. Imagine how much crap will be
> > under the root directory if every kernel subsystem goes there.

What random subsystems do you see under /sys that are better off under
/sys/kernel? Keep in mind, sysfs is an ABI, so moving things is tricky
if it's been in a mainline release.

> > The system is the kernel, afterall, the subsystems should be under
> > there (arguably /sys/kernel/mm/hugepages/ would be better again, in
> > fact yes Nish can we do that?).
> 
> It should be pretty easy. Just need to allocate and add an appropriate
> kobject like kernel_kobj somewhere in the main vm initialization path
> and then change the parent in my patch to be that one rather than
> kernel_kobj.

So I'm ready to start doing this, but am curious if you think you'll
want to move the other mm-related bits under /sys/kernel/mm too (e.g.,
/sys/kernel/slab)? If so, then we'll need to plan for it, as it's an ABI
change. If not, then we might have mm stuff in different locations.

Thanks,
Nish

-- 
Nishanth Aravamudan <nacc@us.ibm.com>
IBM Linux Technology Center

--
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:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2008-07-02  0:27 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-04 11:29 [patch 00/21] hugetlb patches resend npiggin
2008-06-04 11:29 ` [patch 01/21] hugetlb: factor out prep_new_huge_page npiggin
2008-06-04 11:29 ` [patch 02/21] hugetlb: modular state for hugetlb page size npiggin
2008-06-04 11:29 ` [patch 03/21] hugetlb: multiple hstates for multiple page sizes npiggin
2008-06-04 11:29 ` [patch 04/21] hugetlbfs: per mount huge " npiggin
2008-06-04 11:29 ` [patch 05/21] hugetlb: new sysfs interface npiggin
2008-06-08 18:59   ` Andrew Morton
2008-06-10  3:02     ` Nick Piggin
2008-06-12  1:11       ` Nishanth Aravamudan
2008-07-02  0:24         ` Nishanth Aravamudan [this message]
2008-06-20 15:18   ` Dave Hansen
2008-06-23  2:48     ` Nick Piggin
2008-06-23  3:31       ` Andrew Morton
2008-06-23  3:52         ` Nick Piggin
2008-06-04 11:29 ` [patch 06/21] hugetlb: abstract numa round robin selection npiggin
2008-06-04 11:29 ` [patch 07/21] mm: introduce non panic alloc_bootmem npiggin
2008-06-04 11:29 ` [patch 08/21] mm: export prep_compound_page to mm npiggin
2008-06-04 11:29 ` [patch 09/21] hugetlb: support larger than MAX_ORDER npiggin
2008-06-04 11:29 ` [patch 10/21] hugetlb: support boot allocate different sizes npiggin
2008-06-04 11:29 ` [patch 11/21] hugetlb: printk cleanup npiggin
2008-06-04 11:29 ` [patch 12/21] hugetlb: introduce pud_huge npiggin
2008-06-11 23:16   ` Andrew Morton
2008-06-12  0:45     ` Nick Piggin
2008-06-04 11:29 ` [patch 13/21] x86: support GB hugepages on 64-bit npiggin
2008-06-04 11:29 ` [patch 14/21] x86: add hugepagesz option " npiggin
2008-06-04 17:51   ` Randy Dunlap
2008-06-05  2:01     ` Nick Piggin
2008-06-04 11:29 ` [patch 15/21] hugetlb: override default huge page size npiggin
2008-06-09 10:41   ` Andrew Morton
2008-06-10  3:22     ` Nick Piggin
2008-06-04 11:29 ` [patch 16/21] hugetlb: allow arch overried hugepage allocation npiggin
2008-06-08 19:14   ` Andrew Morton
2008-06-10  3:26     ` Nick Piggin
2008-06-12  8:08     ` Andy Whitcroft
2008-06-04 11:29 ` [patch 17/21] powerpc: function to allocate gigantic hugepages npiggin
2008-06-04 11:29 ` [patch 18/21] powerpc: scan device tree for gigantic pages npiggin
2008-06-04 11:29 ` [patch 19/21] powerpc: define support for 16G hugepages npiggin
2008-06-08 19:05   ` Andrew Morton
2008-06-10  3:05     ` Nick Piggin
2008-06-04 11:29 ` [patch 20/21] fs: check for statfs overflow npiggin
2008-06-08 19:06   ` Andrew Morton
2008-06-10  3:12     ` Nick Piggin
2008-06-04 11:30 ` [patch 21/21] powerpc: support multiple hugepage sizes npiggin
2008-07-14 16:32   ` [patch] powerpc: hugetlb pgtable cache access cleanup Jon Tollefson
2008-07-14 16:32     ` Jon Tollefson
2008-07-14 22:56     ` Andrew Morton
2008-07-14 22:56       ` Andrew Morton
2008-07-15 22:49       ` [patch v2] " Jon Tollefson
2008-07-15 22:49         ` Jon Tollefson
2008-07-15 22:57         ` Andrew Morton
2008-07-15 22:57           ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2008-06-03  9:59 [patch 00/21] hugetlb multi size, giant hugetlb support, etc npiggin
2008-06-03 10:00 ` [patch 05/21] hugetlb: new sysfs interface npiggin

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=20080702002431.GA24625@us.ibm.com \
    --to=nacc@us.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.