Re: RFC: Resource Management

Andrew Mileski (dmtech@magi.com)
Mon, 19 Feb 1996 13:20:56 -0500 (EST)

>> >I think it'd be a good idea to include with the "name" (which says what
>> >it is being requested (or what it is requested for)) is "who" ... who is
>> >making the request? Release of a requested region must match on "who" is
>> >releasing ...
>>
>> That was exactly my idea, but I've not come up with a satisfactory 'who'.
>> Any ideas?
>
>If you want to make sure that only the "allocator" be allowed to
>"deallocate", then
--snip--
>Or, have
>the request_hw_region() return a unique handle (like an index in a table
>where the information is stored with a generation number as a part of
>the handle to make it unique should the table entry be reused, or
>including part of the return address of the caller).

This is easily done, but is it enough? It would be possible to
fake another's handle.

>I think something
>generated on the fly would eliminate the need for administration of the
>"who" entry. Actually, returning a unique handle for subsequent release
>requests has always been my preferred method.

Yes, handles have the advantage that they can be passed around.

>How's Ottawa these days? I moved out about 2 years ago because it was
>too cold (not to mention Canadian taxes ;-)

Last time I checked it was -20C (darn cold enough for me).
I've been here 8 years, and I'm not used to it - only 2 seasons,
scorching summer and frigid winter. I miss the other 2 seasons.
This place has a 100C temperature swing!

-- Andrew E. Mileski --

-------------------------------------------------------
Located in Canada's Capital: Ottawa! (EST)
mailto:dmtech@magi.com http://www.magi.com/~dmtech/