чт, 2 мая 2019 г. в 14:23, Joel Savitz :
>
> Yes, this the change, thanks to the suggestion of Yury Norov.
Joel, could you please stop top-posting?
> I also now explicitly mention the expected userspace destination type
> in the manpage patch.
>
> Best,
> Joel Savitz
>
>
> On Thu, May 2, 2019 at
On Thu, May 02, 2019 at 04:52:20PM -0400, Joel Savitz wrote:
> In the mainline kernel, there is no quick mechanism to get the virtual
> memory size of the current process from userspace.
>
> Despite the current state of affairs, this information is available to the
> user through several means, on
Yes, this the change, thanks to the suggestion of Yury Norov.
I also now explicitly mention the expected userspace destination type
in the manpage patch.
Best,
Joel Savitz
On Thu, May 2, 2019 at 5:10 PM Cyrill Gorcunov wrote:
>
> On Thu, May 02, 2019 at 05:01:38PM -0400, Waiman Long wrote:
> >
On Thu, May 02, 2019 at 05:01:38PM -0400, Waiman Long wrote:
>
> What did you change in v2 versus v1?
Seems unsigned long long has been changed to unsigned long.
On 5/2/19 4:52 PM, Joel Savitz wrote:
> In the mainline kernel, there is no quick mechanism to get the virtual
> memory size of the current process from userspace.
>
> Despite the current state of affairs, this information is available to the
> user through several means, one being a linear search
In the mainline kernel, there is no quick mechanism to get the virtual
memory size of the current process from userspace.
Despite the current state of affairs, this information is available to the
user through several means, one being a linear search of the entire address
space. This is an ineffic
6 matches
Mail list logo