public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Fontenot <nfont@austin.ibm.com>
To: 7eggert@gmx.de
Cc: Bodo Eggert <7eggert@web.de>,
	linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] De-couple sysfs memory directories from memory sections
Date: Mon, 12 Jul 2010 21:28:14 -0500	[thread overview]
Message-ID: <4C3BCF3E.7060000@austin.ibm.com> (raw)
In-Reply-To: <20100712194958.1A32B2D6595@mail-in-10.arcor-online.net>

On 07/12/2010 02:30 PM, Bodo Eggert wrote:
> Nathan Fontenot <nfont@austin.ibm.com> wrote:
> 
>> The file 'split' allows for splitting the
>> directory in two, with each new directory covering half as many
>> memory sections as the previous directory.
> 
> Just some random thoughts:
> 1) Why is it needed/helpful?

This is needed if someone needed to perform an action (add/remove) a
single memory section. The 'split' option allows users to isolate
a memory section  so these operations could be performed.

> 2) If it is needed, why not take an int to split after n entries?

The idea of being able to split a directory came out of a previous
discussion on how to resolve the issue this patch set is trying to solve.
I included the split functionality in this patch set since it
was suggested.  I will leave the decision of whether or not this
functionality is needed up to the community.

-Nathan 

  reply	other threads:[~2010-07-13  2:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f5t7d-2ZJ-23@gated-at.bofh.it>
2010-07-12 19:30 ` [PATCH 0/7] De-couple sysfs memory directories from memory sections Bodo Eggert
2010-07-13  2:28   ` Nathan Fontenot [this message]
2010-07-12 15:27 Nathan Fontenot
2010-07-16  7:13 ` Greg KH
2010-07-16 15:41   ` Nathan Fontenot

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=4C3BCF3E.7060000@austin.ibm.com \
    --to=nfont@austin.ibm.com \
    --cc=7eggert@gmx.de \
    --cc=7eggert@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    /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