On Wed, Apr 04, 2007 at 10:03:04PM +0400, Nikita Danilov wrote:
> Matt Mackall writes:
>
> [...]
>
> >
> > Now I could adjust these to only export u64s in some preferred
> > endianness. But given I already need details like the page size to
> > make any sense of it, it seems unnecessary. Als
Matt Mackall writes:
[...]
>
> Now I could adjust these to only export u64s in some preferred
> endianness. But given I already need details like the page size to
> make any sense of it, it seems unnecessary. Also, the PFNs are fairly
> opaque unless you're attempting to correlate them with
On Wed, Apr 04, 2007 at 03:18:41PM +0400, Nikita Danilov wrote:
> This pushes binary data to the user space. Wasn't /proc supposed to be
> ascii-based to avoid compatibility problems (e.g., size of unsigned long
> changing, endianness, etc.)?
Most of what's in /proc is ASCII, true. But there are n
Matt Mackall writes:
> Add /proc/pid/pagemap interface
>
> This interface provides a mapping for each page in an address space to
> its physical page frame number, allowing precise determination of what
> pages are mapped and what pages are shared between processes.
[...]
>
> +#ifdef CO
4 matches
Mail list logo
