On Wednesday, April 18, 2007 03:47:17 PM -0400 chas williams - CONTRACTOR
<[EMAIL PROTECTED]> wrote:
In message
<[EMAIL PROTECTED]>,Derr ick
J Brashear writes:
i am still against the dual mode allocator.
Is your cellphone analog capable?
i am strange enough to have analog mode disabled. however, this isnt
quite the same thing. the "problem" with the "dual mode" allocator
is that it has to remember what kind of memory it allocated so that it
can later free it. it would be better to have an explicity huge memory
allocater.
The problem with this is that it requires every caller to know whether the
thing it is allocating is "huge" or "not huge", where the distinction
depends on the operating system, platform, and perhaps even kernel
configuration. That means we'd be pushing platform-dependent code into
every caller of osi_Alloc, which is exactly what the abstraction is
intended to prevent.
it would also serve to point out sections of the afs code
that could stand some improvement.
No; the size of individual memory allocations is not necessarily an
indicator of code quality.
_______________________________________________
OpenAFS-devel mailing list
[email protected]
https://lists.openafs.org/mailman/listinfo/openafs-devel
