Hmmm ... my previous reaction to this conversion code, when you posted
an ancestor of this patch on linux-mm, got buried in the crypically
terse term 'complex API', and that thread went on to discuss matters
of greater substance, such as whether one thread could or should
manipulate the memory policies of another.
I guess it's time I dealt directly with this code ...
My first suspicion on reading it is that it might partially duplicate
some string conversion code and syntax that is already present in
the kernel for other purposes. For example the nodelists might
replicate the lists of numbers supported by bitmap_scnlistprintf
and bitmap_parselist.
However, since no documentation is presented to describe this new
micro-micro-language for describing memory policies, it is difficult to
know what the syntax is, without reverse engineering it from the code.
So ... how about documenting this string format, then we can discuss
both the syntax and its implementation.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[email protected]> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |