[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: On PATH_MAX
From: |
Jonathan S. Shapiro |
Subject: |
RE: On PATH_MAX |
Date: |
Tue, 08 Nov 2005 14:29:03 -0500 |
On Tue, 2005-11-08 at 10:39 -0700, Christopher Nelson wrote:
> Yeah... I was thinking about that after I wrote it, and I can see how
> that is the case. Does the implementation simply have a user-slidable
> window? Something comparable to a seek, where I can now access that
> memory from byte x to x+n where n is the window size? Or is it
> automated in some fashion?
In EROS, it goes like this:
I'm holding a capability to a memory region that you provided.
I insert this capability into a known slot in my address space
structures. It is now mapped at a known location in my address space.
I now reference it in the usual way using load/store instructions.
shap
- Re: On PATH_MAX, (continued)
RE: On PATH_MAX, Christopher Nelson, 2005/11/08
RE: On PATH_MAX, Christopher Nelson, 2005/11/08
RE: On PATH_MAX, Christopher Nelson, 2005/11/08
RE: On PATH_MAX, Christopher Nelson, 2005/11/08
- RE: On PATH_MAX,
Jonathan S. Shapiro <=
RE: On PATH_MAX, Christopher Nelson, 2005/11/08
RE: On PATH_MAX, Christopher Nelson, 2005/11/08
RE: On PATH_MAX, Christopher Nelson, 2005/11/08
RE: On PATH_MAX, Christopher Nelson, 2005/11/09