On 2020/12/3 2:27, Yang Shi wrote:
The tracepoint's nid should show what node the shrink happens on, the start
tracepoint
uses nid from shrinkctl, but the nid might be set to 0 before end tracepoint if
the
shrinker is not NUMA aware, so the traceing log may show the shrink happens on
one
On 2020/10/22 10:45, Roman Gushchin wrote:
On Thu, Oct 22, 2020 at 09:54:53AM +0800, Xiaqing (A) wrote:
On 2020/10/17 6:52, Roman Gushchin wrote:
This small patchset makes cma_release() non-blocking and simplifies
the code in hugetlbfs, where previously we had to temporarily drop
On 2020/10/17 6:52, Roman Gushchin wrote:
This small patchset makes cma_release() non-blocking and simplifies
the code in hugetlbfs, where previously we had to temporarily drop
hugetlb_lock around the cma_release() call.
It should help Zi Yan on his work on 1 GB THPs: splitting a gigantic
On 2019/2/1 16:15, Dan Carpenter wrote:
On Fri, Feb 01, 2019 at 02:59:46PM +0800, Qing Xia wrote:
In the first loop, gfp_flags will be modified to high_order_gfp_flags,
and there will be no chance to change back to low_order_gfp_flags.
Fixes: e7f63771 ("ION: Sys_heap: Add cached pool to
On 2019/1/3 6:36, Laura Abbott wrote:
On 12/24/18 12:19 AM, Qing Xia wrote:
Now, as Google's user guide, if userspace need clean ION buffer's
cache, they should call ioctl(fd, DMA_BUF_IOCTL_SYNC, sync). Then
we found that ion_dma_buf_begin_cpu_access/ion_dma_buf_end_cpu_access
will do ION
在 2016/5/19 21:18, Catalin Marinas 写道:
On Thu, May 19, 2016 at 01:50:40PM +0100, Catalin Marinas wrote:
On Thu, May 19, 2016 at 07:06:40PM +0800, Xiaqing (A) wrote:
在 2016/5/19 18:49, Catalin Marinas 写道:
On Thu, May 19, 2016 at 10:44:33AM +0800, x00195127 wrote:
we find that some apps
在 2016/5/19 21:18, Catalin Marinas 写道:
On Thu, May 19, 2016 at 01:50:40PM +0100, Catalin Marinas wrote:
On Thu, May 19, 2016 at 07:06:40PM +0800, Xiaqing (A) wrote:
在 2016/5/19 18:49, Catalin Marinas 写道:
On Thu, May 19, 2016 at 10:44:33AM +0800, x00195127 wrote:
we find that some apps
在 2016/5/19 19:04, Robin Murphy 写道:
On 19/05/16 03:44, x00195127 wrote:
we find that some apps will read cpuinfo when start up,
they need the string as follows:
"Processor : AArch64 Processor rev 0 (aarch64)"
Then thay could load the corresponding libs. But now
arm64 platform's
在 2016/5/19 19:04, Robin Murphy 写道:
On 19/05/16 03:44, x00195127 wrote:
we find that some apps will read cpuinfo when start up,
they need the string as follows:
"Processor : AArch64 Processor rev 0 (aarch64)"
Then thay could load the corresponding libs. But now
arm64 platform's
在 2016/5/19 18:49, Catalin Marinas 写道:
On Thu, May 19, 2016 at 10:44:33AM +0800, x00195127 wrote:
we find that some apps will read cpuinfo when start up,
they need the string as follows:
"Processor : AArch64 Processor rev 0 (aarch64)"
Then thay could load the corresponding libs. But
在 2016/5/19 18:49, Catalin Marinas 写道:
On Thu, May 19, 2016 at 10:44:33AM +0800, x00195127 wrote:
we find that some apps will read cpuinfo when start up,
they need the string as follows:
"Processor : AArch64 Processor rev 0 (aarch64)"
Then thay could load the corresponding libs. But
11 matches
Mail list logo
