Re: [Osso-develop] memory interface
Status: Alpha
Brought to you by:
iurlano
From: Eismann <ei...@wa...> - 2002-02-27 23:44:14
|
On Wed, 27 Feb 2002 09:46:06 +0100 (CET) Marco Peccianti <pec...@cl...> wrote: Maybe you haven't understood me, or I haven't understood you. > > What about logical memory manager functions? > > And, will the kernel manage page directories and tables like now in message > > functions, create process functions and others? > > Well, not really the kernel (in the sense that is not centralized). Yes, I'm talking about inerface between kernel and mem manager. The two things are the kernel. With mem manager I refer to kernel mem manager subsistem, and with kernel to the rest of the kernel. > > I think it would be better (more clear) if the kernel touches this things > > the minimum possible. Example. Now in getbmsg() from messages.c, it asks for pages and it maps the pages to process linear memory. I'm saying to do this into memory manager (that it is into the kernel too). > [Process: I need 30 pages] > <Kernel: Take them!> > > Obiviously this is serialized, cause only one process a time (tricks > excluded) can use the data structures describing global memory. It handles > only pages, to make it as fast as possible. > It's interface is a kernel function, called internally. > > 2) Logical mapper: > It maps the pages obtained before where the process needs, and use it for > program starting, heap, messages and so on. > Obiviously at this level there are no process interaction, so things can > be done in parallel. > It's interface is made by getmesg(), or Mallosso(), or everything needs to > map memory onto process space. The process requests for memory with mallosso(), and mallosso() requests for pages to the physical memory manager?. This is what I was thinking... Excuse me if I haven't understood you and I 've confused more the things. Aitor |