Re: More on garbage collection
From: Nick Maclaren (nmm1_at_cus.cam.ac.uk)
Date: 06/13/05
- Next message: Nick Maclaren: "Re: Ancient history"
- Previous message: Andrew Swallow: "Re: Public disclosure of discovered vulnerabilities"
- In reply to: Stefan Monnier: "Re: More on garbage collection"
- Next in thread: Stefan Monnier: "Re: More on garbage collection"
- Reply: Stefan Monnier: "Re: More on garbage collection"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: 13 Jun 2005 16:36:15 GMT
In article <87d5qq495z.fsf-monnier+comp.arch@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> |>
>> |> I wasn't just thinking of the area/zone/foo-based memory management
>> |> that existed back then, but more specifically of the more recent
>> |> variants where the deallocation is checked (either statically or
>> |> dynamically) to guarantee the "absence" of leaks and to prevent
>> |> dangling pointer dereference.
>
>> Yes, that is what I was doing then. It isn't hard.
>
>That's news to me. Could you point me to relevant material?
No. As I said, we regarded it as trivial and Just Did It. It is
only recently that people have been publishing claims that it is a
great new invention.
>> See my other postings. Difficulties in specifying contiguity,
>> alignment and so on, as well as in finding out how much space has
>> been used and is free. The problems redouble in spades when you
>> need to do either of these for physical memory rather than just
>> virtual.
>
>Sounds pretty vague to me. I mean I understand what is contiguity and
>alignment, but I'm not sure what you would consider as a solution.
>
>E.g. what do you actually use, and consider good memory
>management primitives for your HPC codes?
None that currently exist :-(
As a simple example, one thing that I should like to do is the following:
Get a physically contiguous area of data of length N, aligned at
2^K but not at the same 2^L alignment as pointers P and Q. And
preserve those properties, swapping or cancelling the process
rather than breaking them, if necessary.
It would be better to have a more portable description of such aspects,
but that would need more design than I have time for now.
Regards,
Nick Maclaren.
- Next message: Nick Maclaren: "Re: Ancient history"
- Previous message: Andrew Swallow: "Re: Public disclosure of discovered vulnerabilities"
- In reply to: Stefan Monnier: "Re: More on garbage collection"
- Next in thread: Stefan Monnier: "Re: More on garbage collection"
- Reply: Stefan Monnier: "Re: More on garbage collection"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|