On 9/18/20 11:18 PM, Waiman Long wrote:
On 9/18/20 2:44 AM, Xu, Yanfei wrote:
Hi Waiman,
On 8/12/20 6:29 AM, Andrew Morton wrote:
On Thu, 18 Jun 2020 17:29:36 -0400 Waiman Long
wrote:
The current_gfp_context() converts a number of PF_MEMALLOC_*
per-process
flags into the corresponding
On 9/18/20 2:44 AM, Xu, Yanfei wrote:
Hi Waiman,
On 8/12/20 6:29 AM, Andrew Morton wrote:
On Thu, 18 Jun 2020 17:29:36 -0400 Waiman Long
wrote:
The current_gfp_context() converts a number of PF_MEMALLOC_*
per-process
flags into the corresponding GFP_* flags for memory allocation. In
that f
Hi Waiman,
On 8/12/20 6:29 AM, Andrew Morton wrote:
On Thu, 18 Jun 2020 17:29:36 -0400 Waiman Long wrote:
The current_gfp_context() converts a number of PF_MEMALLOC_* per-process
flags into the corresponding GFP_* flags for memory allocation. In
that function, current->flags is accessed 3 tim
On 8/11/20 6:29 PM, Andrew Morton wrote:
On Thu, 18 Jun 2020 17:29:36 -0400 Waiman Long wrote:
The current_gfp_context() converts a number of PF_MEMALLOC_* per-process
flags into the corresponding GFP_* flags for memory allocation. In
that function, current->flags is accessed 3 times. That may
On Thu, 18 Jun 2020 17:29:36 -0400 Waiman Long wrote:
> The current_gfp_context() converts a number of PF_MEMALLOC_* per-process
> flags into the corresponding GFP_* flags for memory allocation. In
> that function, current->flags is accessed 3 times. That may lead to
> duplicated access of the sa
The current_gfp_context() converts a number of PF_MEMALLOC_* per-process
flags into the corresponding GFP_* flags for memory allocation. In
that function, current->flags is accessed 3 times. That may lead to
duplicated access of the same memory location.
This is not usually a problem with minimal
6 matches
Mail list logo