From: Paul Jackson <pj@sgi.com>
To: Christoph Lameter <christoph@lameter.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] String conversions for memory policy
Date: Fri, 29 Jul 2005 22:54:32 -0700 [thread overview]
Message-ID: <20050729225432.63b3dfb0.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0507291746000.8663@graphe.net>
Christoph wrote:
> you could have a look at my initial patch which actually
> included a description of the syntax
Yes - I could (I did actually).
Something like that should be part of the record here. Not everyone
has your earlier linux-mm email thread right at hand.
> Diff to use bitmap_scnlistprintf and bitmap_parselist.
That was quick - thanks.
Once we have a clear description of this syntax in the record,
I anticipate raising as an issue that this syntax does not have a
single integer or string token value per file (or at most, an array
or list of comparable integer values).
But first things first. Until any lurkers can easily see what is being
proposed, it is inconvenient to carry on discussions of alternatives
and their relative merits.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2005-07-30 5:54 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 18:38 [PATCH] String conversions for memory policy Christoph Lameter
2005-07-29 22:20 ` Paul Jackson
2005-07-30 0:53 ` Christoph Lameter
2005-07-30 5:54 ` Paul Jackson [this message]
2005-07-30 15:48 ` Christoph Lameter
2005-07-31 1:45 ` Paul Jackson
2005-07-30 6:00 ` Paul Jackson
2005-07-30 17:56 ` Christoph Lameter
2005-07-31 1:14 ` Paul Jackson
2005-07-31 1:21 ` Christoph Lameter
2005-07-31 1:50 ` Paul Jackson
2005-07-31 2:01 ` Paul Jackson
2005-07-31 2:05 ` Christoph Lameter
2005-07-31 2:12 ` Paul Jackson
2005-07-31 2:15 ` Christoph Lameter
2005-08-01 18:48 ` Christoph Lameter
2005-08-01 18:54 ` Christoph Lameter
2005-08-01 23:03 ` Paul Jackson
2005-08-01 23:24 ` Christoph Lameter
2005-08-01 23:59 ` Paul Jackson
2005-08-02 0:03 ` Christoph Lameter
2005-08-02 0:15 ` Christoph Lameter
2005-08-02 5:33 ` Paul Jackson
2005-08-02 6:11 ` Christoph Lameter
2005-08-03 5:44 ` Paul Jackson
2005-08-03 16:19 ` Christoph Lameter
2005-08-02 17:49 ` Christoph Lameter
2005-08-03 5:42 ` Paul Jackson
2005-08-03 8:48 ` Andi Kleen
2005-08-04 14:11 ` Christoph Lameter
2005-08-04 14:29 ` Andi Kleen
2005-08-04 16:31 ` Christoph Lameter
2005-08-04 17:08 ` Andi Kleen
2005-08-04 17:34 ` NUMA policy interface Christoph Lameter
2005-08-04 21:14 ` Andi Kleen
2005-08-04 21:21 ` Christoph Lameter
2005-08-04 21:41 ` Andi Kleen
2005-08-04 22:19 ` Christoph Lameter
2005-08-04 22:44 ` Mike Kravetz
2005-08-04 23:40 ` Andi Kleen
2005-08-04 23:49 ` Christoph Lameter
2005-08-05 9:16 ` Andi Kleen
2005-08-05 14:52 ` Christoph Lameter
2005-08-05 14:58 ` Christoph Lameter
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=20050729225432.63b3dfb0.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@osdl.org \
--cc=christoph@lameter.com \
--cc=linux-kernel@vger.kernel.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