Messages in this thread | | | Date | Thu, 14 Jul 2011 13:23:28 -0700 | From | "H. Peter Anvin" <> | Subject | Re: [PATCH 13/13] memblock, x86: Replace memblock_x86_reserve/free_range() with generic ones |
| |
On 07/14/2011 01:20 PM, Tejun Heo wrote: > > Hmm... looking at the boot log, not really. [ ) ranges are more > common. memblock code is one of notable exceptions and I actually was > thinking about converting it. [ ) ranges are easier to recognize and > most of code we have can't deal with the full range (and it shouldn't > need to - chopping off one top and bottom is much saner approach > anyway). >
Sorry I don't follow. We display resources as [...] ranges, and in particular when there are those kinds of brackets they tend to be inclusive ranges.
For the internal representation, of course, [ ) ranges or (base, length) are the only sensible options.
-hpa
| |