Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

On Tue, Oct 24, 2017 at 10:12:58AM +0200, Vlastimil Babka wrote: > On 10/24/2017 06:44 AM, Joonsoo Kim wrote: > >>> I'm not sure what is the confusing semantic you mentioned. I think > >>> that set_migratetype_isolate() has confusing semantic and should be > >&g

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

On Tue, Oct 24, 2017 at 10:12:58AM +0200, Vlastimil Babka wrote: > On 10/24/2017 06:44 AM, Joonsoo Kim wrote: > >>> I'm not sure what is the confusing semantic you mentioned. I think > >>> that set_migratetype_isolate() has confusing semantic and should be > >&g

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

On Mon, Oct 23, 2017 at 10:10:09AM +0200, Michal Hocko wrote: > On Mon 23-10-17 14:23:09, Joonsoo Kim wrote: > > On Fri, Oct 20, 2017 at 09:02:20AM +0200, Michal Hocko wrote: > > > On Fri 20-10-17 15:50:14, Joonsoo Kim wrote: > > > > On Fri, Oct 20, 2017 at 07:59:

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

On Mon, Oct 23, 2017 at 10:10:09AM +0200, Michal Hocko wrote: > On Mon 23-10-17 14:23:09, Joonsoo Kim wrote: > > On Fri, Oct 20, 2017 at 09:02:20AM +0200, Michal Hocko wrote: > > > On Fri 20-10-17 15:50:14, Joonsoo Kim wrote: > > > > On Fri, Oct 20, 2017 at 07:59:

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

On Fri, Oct 20, 2017 at 10:17:00AM +0200, Michal Hocko wrote: > On Fri 20-10-17 15:22:14, Xishi Qiu wrote: > > On 2017/10/20 10:13, Joonsoo Kim wrote: > > > > > On Thu, Oct 19, 2017 at 02:21:18PM +0200, Michal Hocko wrote: > [...] > > >> >From 8cbd811d7

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

On Fri, Oct 20, 2017 at 10:17:00AM +0200, Michal Hocko wrote: > On Fri 20-10-17 15:22:14, Xishi Qiu wrote: > > On 2017/10/20 10:13, Joonsoo Kim wrote: > > > > > On Thu, Oct 19, 2017 at 02:21:18PM +0200, Michal Hocko wrote: > [...] > > >> >From 8cbd811d7

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

On Fri, Oct 20, 2017 at 09:02:20AM +0200, Michal Hocko wrote: > On Fri 20-10-17 15:50:14, Joonsoo Kim wrote: > > On Fri, Oct 20, 2017 at 07:59:22AM +0200, Michal Hocko wrote: > > > On Fri 20-10-17 11:13:29, Joonsoo Kim wrote: > > > > On Thu, Oct 19, 2017 at 02:21:

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

On Fri, Oct 20, 2017 at 09:02:20AM +0200, Michal Hocko wrote: > On Fri 20-10-17 15:50:14, Joonsoo Kim wrote: > > On Fri, Oct 20, 2017 at 07:59:22AM +0200, Michal Hocko wrote: > > > On Fri 20-10-17 11:13:29, Joonsoo Kim wrote: > > > > On Thu, Oct 19, 2017 at 02:21:

Re: n900 in next-20170901

On Fri, Oct 20, 2017 at 10:31:47AM -0700, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo@lge.com> [171019 18:53]: > > Oops... I made a mistak. Could you test with reverting commit > > c977ee2803787363187d6aca9cebdabc793c6531 ("omap: forcibly call > > sa

Re: n900 in next-20170901

On Fri, Oct 20, 2017 at 10:31:47AM -0700, Tony Lindgren wrote: > * Joonsoo Kim [171019 18:53]: > > Oops... I made a mistak. Could you test with reverting commit > > c977ee2803787363187d6aca9cebdabc793c6531 ("omap: forcibly call > > save_secure_ram_context() for test&quo

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

On Fri, Oct 20, 2017 at 07:59:22AM +0200, Michal Hocko wrote: > On Fri 20-10-17 11:13:29, Joonsoo Kim wrote: > > On Thu, Oct 19, 2017 at 02:21:18PM +0200, Michal Hocko wrote: > > > On Thu 19-10-17 10:20:41, Michal Hocko wrote: > > > > On Thu 19-10-17 16:33:56, Joons

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

On Fri, Oct 20, 2017 at 07:59:22AM +0200, Michal Hocko wrote: > On Fri 20-10-17 11:13:29, Joonsoo Kim wrote: > > On Thu, Oct 19, 2017 at 02:21:18PM +0200, Michal Hocko wrote: > > > On Thu 19-10-17 10:20:41, Michal Hocko wrote: > > > > On Thu 19-10-17 16:33:56, Joons

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

On Thu, Oct 19, 2017 at 02:21:18PM +0200, Michal Hocko wrote: > On Thu 19-10-17 10:20:41, Michal Hocko wrote: > > On Thu 19-10-17 16:33:56, Joonsoo Kim wrote: > > > On Thu, Oct 19, 2017 at 09:15:03AM +0200, Michal Hocko wrote: > > > > On Thu 19-10-

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

On Thu, Oct 19, 2017 at 02:21:18PM +0200, Michal Hocko wrote: > On Thu 19-10-17 10:20:41, Michal Hocko wrote: > > On Thu 19-10-17 16:33:56, Joonsoo Kim wrote: > > > On Thu, Oct 19, 2017 at 09:15:03AM +0200, Michal Hocko wrote: > > > > On Thu 19-10-

Re: n900 in next-20170901

On Thu, Oct 19, 2017 at 11:30:34AM -0700, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo@lge.com> [171018 01:27]: > > On Mon, Sep 25, 2017 at 07:54:37AM -0700, Tony Lindgren wrote: > > > * Joonsoo Kim <iamjoonsoo@lge.com> [170925 01:06]: > > > >

Re: n900 in next-20170901

On Thu, Oct 19, 2017 at 11:30:34AM -0700, Tony Lindgren wrote: > * Joonsoo Kim [171018 01:27]: > > On Mon, Sep 25, 2017 at 07:54:37AM -0700, Tony Lindgren wrote: > > > * Joonsoo Kim [170925 01:06]: > > > > On Thu, Sep 21, 2017 at 10:28:11AM -0700, Tony Lindgren

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

On Thu, Oct 19, 2017 at 09:15:03AM +0200, Michal Hocko wrote: > On Thu 19-10-17 11:51:11, Joonsoo Kim wrote: > > On Fri, Oct 13, 2017 at 02:00:12PM +0200, Michal Hocko wrote: > > > From: Michal Hocko <mho...@suse.com> > > > > > > Michael has noticed that

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

On Thu, Oct 19, 2017 at 09:15:03AM +0200, Michal Hocko wrote: > On Thu 19-10-17 11:51:11, Joonsoo Kim wrote: > > On Fri, Oct 13, 2017 at 02:00:12PM +0200, Michal Hocko wrote: > > > From: Michal Hocko > > > > > > Michael has noticed that the memory offline trie

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

On Fri, Oct 13, 2017 at 02:00:12PM +0200, Michal Hocko wrote: > From: Michal Hocko > > Michael has noticed that the memory offline tries to migrate kernel code > pages when doing > echo 0 > /sys/devices/system/memory/memory0/online > > The current implementation will fail the

Re: [PATCH 1/2] mm: drop migrate type checks from has_unmovable_pages

On Fri, Oct 13, 2017 at 02:00:12PM +0200, Michal Hocko wrote: > From: Michal Hocko > > Michael has noticed that the memory offline tries to migrate kernel code > pages when doing > echo 0 > /sys/devices/system/memory/memory0/online > > The current implementation will fail the operation after

Re: [lkp-robot] [x86/kconfig] 81d3871900: BUG:unable_to_handle_kernel

On Wed, Oct 18, 2017 at 03:15:03PM +0200, Thomas Gleixner wrote: > On Wed, 18 Oct 2017, Linus Torvalds wrote: > > On Tue, Oct 17, 2017 at 3:33 AM, Joonsoo Kim <iamjoonsoo@lge.com> wrote: > > > > > > It looks like a compiler bug. The code of slob_un

Re: [lkp-robot] [x86/kconfig] 81d3871900: BUG:unable_to_handle_kernel

On Wed, Oct 18, 2017 at 03:15:03PM +0200, Thomas Gleixner wrote: > On Wed, 18 Oct 2017, Linus Torvalds wrote: > > On Tue, Oct 17, 2017 at 3:33 AM, Joonsoo Kim wrote: > > > > > > It looks like a compiler bug. The code of slob_units() try to read two > > > b

Re: n900 in next-20170901

On Mon, Sep 25, 2017 at 07:54:37AM -0700, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo@lge.com> [170925 01:06]: > > On Thu, Sep 21, 2017 at 10:28:11AM -0700, Tony Lindgren wrote: > > > * Joonsoo Kim <iamjoonsoo@lge.com> [170914 23:55]: > > > >

Re: n900 in next-20170901

On Mon, Sep 25, 2017 at 07:54:37AM -0700, Tony Lindgren wrote: > * Joonsoo Kim [170925 01:06]: > > On Thu, Sep 21, 2017 at 10:28:11AM -0700, Tony Lindgren wrote: > > > * Joonsoo Kim [170914 23:55]: > > > > On Wed, Sep 13, 2017 at 09:31:27AM -0700, Tony Lindgren w

Re: [lkp-robot] [x86/kconfig] 81d3871900: BUG:unable_to_handle_kernel

On Tue, Oct 17, 2017 at 09:50:04AM +0200, Thomas Gleixner wrote: > On Tue, 17 Oct 2017, Joonsoo Kim wrote: > > On Wed, Oct 11, 2017 at 12:01:20PM -0500, Josh Poimboeuf wrote: > > > > Looking at the panic, the code in slob_free() was: > > > > > > &g

Re: [lkp-robot] [x86/kconfig] 81d3871900: BUG:unable_to_handle_kernel

On Tue, Oct 17, 2017 at 09:50:04AM +0200, Thomas Gleixner wrote: > On Tue, 17 Oct 2017, Joonsoo Kim wrote: > > On Wed, Oct 11, 2017 at 12:01:20PM -0500, Josh Poimboeuf wrote: > > > > Looking at the panic, the code in slob_free() was: > > > > > > &g

Re: [lkp-robot] [x86/kconfig] 81d3871900: BUG:unable_to_handle_kernel

On Wed, Oct 11, 2017 at 12:01:20PM -0500, Josh Poimboeuf wrote: > I failed to add the slab maintainers to CC on the last attempt. Trying > again. > > On Tue, Oct 10, 2017 at 09:31:06PM -0500, Josh Poimboeuf wrote: > > On Tue, Oct 10, 2017 at 08:15:13PM +0800, kernel test robot wrote: > > > > >

Re: [lkp-robot] [x86/kconfig] 81d3871900: BUG:unable_to_handle_kernel

On Wed, Oct 11, 2017 at 12:01:20PM -0500, Josh Poimboeuf wrote: > I failed to add the slab maintainers to CC on the last attempt. Trying > again. > > On Tue, Oct 10, 2017 at 09:31:06PM -0500, Josh Poimboeuf wrote: > > On Tue, Oct 10, 2017 at 08:15:13PM +0800, kernel test robot wrote: > > > > >

Re: n900 in next-20170901

On Thu, Sep 21, 2017 at 10:28:11AM -0700, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo@lge.com> [170914 23:55]: > > On Wed, Sep 13, 2017 at 09:31:27AM -0700, Tony Lindgren wrote: > > > Yes I disabled CONFIG_HIGHMEM and n900 boots. To disable it, > > > yo

Re: n900 in next-20170901

On Thu, Sep 21, 2017 at 10:28:11AM -0700, Tony Lindgren wrote: > * Joonsoo Kim [170914 23:55]: > > On Wed, Sep 13, 2017 at 09:31:27AM -0700, Tony Lindgren wrote: > > > Yes I disabled CONFIG_HIGHMEM and n900 boots. To disable it, > > > you need to remove it from

Re: n900 in next-20170901

Hello, On Fri, Sep 15, 2017 at 03:28:44PM +0200, Pali Rohár wrote: > On Thursday 07 September 2017 16:30:38 Joonsoo Kim wrote: > > If it doesn't help, is there a way to test n900 configuration in QEMU? > > Hi Joonsoo, linaro version of QEMU has support for n900 machine. For >

Re: n900 in next-20170901

Hello, On Fri, Sep 15, 2017 at 03:28:44PM +0200, Pali Rohár wrote: > On Thursday 07 September 2017 16:30:38 Joonsoo Kim wrote: > > If it doesn't help, is there a way to test n900 configuration in QEMU? > > Hi Joonsoo, linaro version of QEMU has support for n900 machine. For >

Re: n900 in next-20170901

On Fri, Sep 15, 2017 at 03:18:18PM +0200, Pavel Machek wrote: > Hi! > > > > After commit 9caf25f996e8, user for CMA memory should use to check > > > PageHighmem in order to get proper virtual address of the page. If > > > someone doesn't use it, it is possible to use wrong virtual address > > >

Re: n900 in next-20170901

On Fri, Sep 15, 2017 at 03:18:18PM +0200, Pavel Machek wrote: > Hi! > > > > After commit 9caf25f996e8, user for CMA memory should use to check > > > PageHighmem in order to get proper virtual address of the page. If > > > someone doesn't use it, it is possible to use wrong virtual address > > >

Re: n900 in next-20170901

On Wed, Sep 13, 2017 at 09:31:27AM -0700, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo@lge.com> [170913 00:54]: > > On Thu, Sep 07, 2017 at 09:16:51AM -0700, Tony Lindgren wrote: > > > I doubt that QEMU n900 boots in secure mode but instead shows > > > the

Re: n900 in next-20170901

On Wed, Sep 13, 2017 at 09:31:27AM -0700, Tony Lindgren wrote: > * Joonsoo Kim [170913 00:54]: > > On Thu, Sep 07, 2017 at 09:16:51AM -0700, Tony Lindgren wrote: > > > I doubt that QEMU n900 boots in secure mode but instead shows > > > the SoC as general purpose SoC.

Re: n900 in next-20170901

On Thu, Sep 07, 2017 at 09:16:51AM -0700, Tony Lindgren wrote: > * Joonsoo Kim <iamjoonsoo@lge.com> [170907 00:30]: > > On Wed, Sep 06, 2017 at 06:30:57AM -0700, Tony Lindgren wrote: > > > Hi, > > > > > > * Joonsoo Kim <iamjoonsoo@lge.com

Re: n900 in next-20170901

On Thu, Sep 07, 2017 at 09:16:51AM -0700, Tony Lindgren wrote: > * Joonsoo Kim [170907 00:30]: > > On Wed, Sep 06, 2017 at 06:30:57AM -0700, Tony Lindgren wrote: > > > Hi, > > > > > > * Joonsoo Kim [170905 16:32]: > > > > I think that I m

Re: n900 in next-20170901

On Wed, Sep 06, 2017 at 06:30:57AM -0700, Tony Lindgren wrote: > Hi, > > * Joonsoo Kim <iamjoonsoo@lge.com> [170905 16:32]: > > I think that I made a mistake for configuration CONFIG_HIGHMEM=y and > > CONFIG_HAVE_MEMBLOCK_NODE_MAP=y. In this case, the MOVABLE_ZONE c

Re: n900 in next-20170901

On Wed, Sep 06, 2017 at 06:30:57AM -0700, Tony Lindgren wrote: > Hi, > > * Joonsoo Kim [170905 16:32]: > > I think that I made a mistake for configuration CONFIG_HIGHMEM=y and > > CONFIG_HAVE_MEMBLOCK_NODE_MAP=y. In this case, the MOVABLE_ZONE can > > be *!highmem*

Re: n900 in next-20170901

On Tue, Sep 05, 2017 at 01:13:15PM -0700, Tony Lindgren wrote: > * Pavel Machek [170903 13:38]: > > Hi! > > > > It compiles ok, but it hangs on boot; black screen, so sometime before > > display is initialized. > > Thanks for reporting it. Based on git bisect, the regression

Re: n900 in next-20170901

On Tue, Sep 05, 2017 at 01:13:15PM -0700, Tony Lindgren wrote: > * Pavel Machek [170903 13:38]: > > Hi! > > > > It compiles ok, but it hangs on boot; black screen, so sometime before > > display is initialized. > > Thanks for reporting it. Based on git bisect, the regression causing > commit is

Re: [PATCH] mm/page_alloc: don't reserve ZONE_HIGHMEM for ZONE_MOVABLE request

On Tue, Aug 29, 2017 at 03:39:45PM +0200, Michal Hocko wrote: > On Tue 29-08-17 09:45:47, Joonsoo Kim wrote: > > On Mon, Aug 28, 2017 at 11:56:16AM +0200, Michal Hocko wrote: > > > On Mon 28-08-17 09:15:52, Joonsoo Kim wrote: > > > > On Fri, Aug 25, 2017 at 09:38:

Re: [PATCH] mm/page_alloc: don't reserve ZONE_HIGHMEM for ZONE_MOVABLE request

On Tue, Aug 29, 2017 at 03:39:45PM +0200, Michal Hocko wrote: > On Tue 29-08-17 09:45:47, Joonsoo Kim wrote: > > On Mon, Aug 28, 2017 at 11:56:16AM +0200, Michal Hocko wrote: > > > On Mon 28-08-17 09:15:52, Joonsoo Kim wrote: > > > > On Fri, Aug 25, 2017 at 09:38:

Re: [PATCH 2/2] mm/slub: don't use reserved highatomic pageblock for optimistic try

On Tue, Aug 29, 2017 at 09:33:44AM +0900, Joonsoo Kim wrote: > On Mon, Aug 28, 2017 at 03:08:29PM +0200, Michal Hocko wrote: > > On Mon 28-08-17 13:29:29, Vlastimil Babka wrote: > > > On 08/28/2017 03:11 AM, js1...@gmail.com wrote: > > > > From: Joons

Re: [PATCH 2/2] mm/slub: don't use reserved highatomic pageblock for optimistic try

On Tue, Aug 29, 2017 at 09:33:44AM +0900, Joonsoo Kim wrote: > On Mon, Aug 28, 2017 at 03:08:29PM +0200, Michal Hocko wrote: > > On Mon 28-08-17 13:29:29, Vlastimil Babka wrote: > > > On 08/28/2017 03:11 AM, js1...@gmail.com wrote: > > > > From: Joonsoo Kim >

Re: [PATCH 1/3] mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE

On Tue, Aug 29, 2017 at 11:16:18AM +0200, Vlastimil Babka wrote: > On 08/24/2017 08:36 AM, js1...@gmail.com wrote: > > From: Joonsoo Kim <iamjoonsoo@lge.com> > > > > 0. History > > > > This patchset is the follow-up of the discussion about the &g

Re: [PATCH 1/3] mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE

On Tue, Aug 29, 2017 at 11:16:18AM +0200, Vlastimil Babka wrote: > On 08/24/2017 08:36 AM, js1...@gmail.com wrote: > > From: Joonsoo Kim > > > > 0. History > > > > This patchset is the follow-up of the discussion about the > > "Introduce ZON

Re: [PATCH] mm/page_alloc: don't reserve ZONE_HIGHMEM for ZONE_MOVABLE request

On Mon, Aug 28, 2017 at 11:56:16AM +0200, Michal Hocko wrote: > On Mon 28-08-17 09:15:52, Joonsoo Kim wrote: > > On Fri, Aug 25, 2017 at 09:38:42AM +0200, Michal Hocko wrote: > > > On Fri 25-08-17 09:20:31, Joonsoo Kim wrote: > > > > On Thu, Aug 24, 2017 at 11:41:58A

Re: [PATCH] mm/page_alloc: don't reserve ZONE_HIGHMEM for ZONE_MOVABLE request

On Mon, Aug 28, 2017 at 11:56:16AM +0200, Michal Hocko wrote: > On Mon 28-08-17 09:15:52, Joonsoo Kim wrote: > > On Fri, Aug 25, 2017 at 09:38:42AM +0200, Michal Hocko wrote: > > > On Fri 25-08-17 09:20:31, Joonsoo Kim wrote: > > > > On Thu, Aug 24, 2017 at 11:41:58A

Re: [PATCH] mm/page_alloc: don't reserve ZONE_HIGHMEM for ZONE_MOVABLE request

On Mon, Aug 28, 2017 at 08:45:07AM +0200, Vlastimil Babka wrote: > +CC linux-api > > On 08/28/2017 02:28 AM, Joonsoo Kim wrote: > > On Fri, Aug 25, 2017 at 09:56:10AM +0200, Vlastimil Babka wrote: > >> On 08/25/2017 02:20 AM, Joonsoo Kim wrote: > >>> On T

Re: [PATCH] mm/page_alloc: don't reserve ZONE_HIGHMEM for ZONE_MOVABLE request

On Mon, Aug 28, 2017 at 08:45:07AM +0200, Vlastimil Babka wrote: > +CC linux-api > > On 08/28/2017 02:28 AM, Joonsoo Kim wrote: > > On Fri, Aug 25, 2017 at 09:56:10AM +0200, Vlastimil Babka wrote: > >> On 08/25/2017 02:20 AM, Joonsoo Kim wrote: > >>> On T

Re: [PATCH 2/2] mm/slub: don't use reserved highatomic pageblock for optimistic try

On Mon, Aug 28, 2017 at 03:08:29PM +0200, Michal Hocko wrote: > On Mon 28-08-17 13:29:29, Vlastimil Babka wrote: > > On 08/28/2017 03:11 AM, js1...@gmail.com wrote: > > > From: Joonsoo Kim <iamjoonsoo@lge.com> > > > > > > High-order atomic allocati

Re: [PATCH 2/2] mm/slub: don't use reserved highatomic pageblock for optimistic try

On Mon, Aug 28, 2017 at 03:08:29PM +0200, Michal Hocko wrote: > On Mon 28-08-17 13:29:29, Vlastimil Babka wrote: > > On 08/28/2017 03:11 AM, js1...@gmail.com wrote: > > > From: Joonsoo Kim > > > > > > High-order atomic allocation is difficult to succeed si

Re: [PATCH 1/2] mm/slub: wake up kswapd for initial high order allocation

On Mon, Aug 28, 2017 at 12:04:41PM +0200, Vlastimil Babka wrote: > On 08/28/2017 03:11 AM, js1...@gmail.com wrote: > > From: Joonsoo Kim <iamjoonsoo@lge.com> > > > > slub uses higher order allocation than it actually needs. In this case, > > we don't

Re: [PATCH 1/2] mm/slub: wake up kswapd for initial high order allocation

On Mon, Aug 28, 2017 at 12:04:41PM +0200, Vlastimil Babka wrote: > On 08/28/2017 03:11 AM, js1...@gmail.com wrote: > > From: Joonsoo Kim > > > > slub uses higher order allocation than it actually needs. In this case, > > we don't want to do direct reclaim to make s

Re: [PATCH] mm/page_alloc: don't reserve ZONE_HIGHMEM for ZONE_MOVABLE request

On Fri, Aug 25, 2017 at 09:56:10AM +0200, Vlastimil Babka wrote: > On 08/25/2017 02:20 AM, Joonsoo Kim wrote: > > On Thu, Aug 24, 2017 at 11:41:58AM +0200, Vlastimil Babka wrote: > > > > Hmm, this is already pointed by Minchan and I have answered that. > > > >

Re: [PATCH] mm/page_alloc: don't reserve ZONE_HIGHMEM for ZONE_MOVABLE request

On Fri, Aug 25, 2017 at 09:56:10AM +0200, Vlastimil Babka wrote: > On 08/25/2017 02:20 AM, Joonsoo Kim wrote: > > On Thu, Aug 24, 2017 at 11:41:58AM +0200, Vlastimil Babka wrote: > > > > Hmm, this is already pointed by Minchan and I have answered that. > > > >

Re: [PATCH 0/3] mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE

On Fri, Aug 25, 2017 at 02:32:13PM -0700, Andrew Morton wrote: > On Thu, 24 Aug 2017 15:36:30 +0900 js1...@gmail.com wrote: > > > From: Joonsoo Kim <iamjoonsoo@lge.com> > > > > This patchset is the follow-up of the discussion about the > > "Intro

Re: [PATCH 0/3] mm/cma: manage the memory of the CMA area by using the ZONE_MOVABLE

On Fri, Aug 25, 2017 at 02:32:13PM -0700, Andrew Morton wrote: > On Thu, 24 Aug 2017 15:36:30 +0900 js1...@gmail.com wrote: > > > From: Joonsoo Kim > > > > This patchset is the follow-up of the discussion about the > > "Introduce ZONE_CMA (v7)" [1].

Re: [PATCH] mm/page_alloc: don't reserve ZONE_HIGHMEM for ZONE_MOVABLE request

On Fri, Aug 25, 2017 at 09:38:42AM +0200, Michal Hocko wrote: > On Fri 25-08-17 09:20:31, Joonsoo Kim wrote: > > On Thu, Aug 24, 2017 at 11:41:58AM +0200, Vlastimil Babka wrote: > > > On 08/24/2017 07:45 AM, js1...@gmail.com wrote: > > > > From: Joons

Re: [PATCH] mm/page_alloc: don't reserve ZONE_HIGHMEM for ZONE_MOVABLE request

On Fri, Aug 25, 2017 at 09:38:42AM +0200, Michal Hocko wrote: > On Fri 25-08-17 09:20:31, Joonsoo Kim wrote: > > On Thu, Aug 24, 2017 at 11:41:58AM +0200, Vlastimil Babka wrote: > > > On 08/24/2017 07:45 AM, js1...@gmail.com wrote: > > > > From: Joonsoo

Re: [PATCH] zram: add zstd to the supported algorithms list

On Fri, Aug 25, 2017 at 01:35:35AM +, Nick Terrell wrote: > On 8/24/17, 5:49 PM, "Joonsoo Kim" <iamjoonsoo@lge.com> wrote: > > On Thu, Aug 24, 2017 at 09:33:54PM +, Nick Terrell wrote: > > > On Thu, Aug 24, 2017 at 10:49:36AM +0900, Sergey S

Re: [PATCH] zram: add zstd to the supported algorithms list

On Fri, Aug 25, 2017 at 01:35:35AM +, Nick Terrell wrote: > On 8/24/17, 5:49 PM, "Joonsoo Kim" wrote: > > On Thu, Aug 24, 2017 at 09:33:54PM +, Nick Terrell wrote: > > > On Thu, Aug 24, 2017 at 10:49:36AM +0900, Sergey Senozhatsky wrote: > > >

Re: [PATCH] zram: add zstd to the supported algorithms list

On Thu, Aug 24, 2017 at 09:33:54PM +, Nick Terrell wrote: > On Thu, Aug 24, 2017 at 10:49:36AM +0900, Sergey Senozhatsky wrote: > > Add ZSTD to the list of supported compression algorithms. > > > > Official benchmarks [1]: > > Awesome! Let me know if you need anything from me. > Hello,

Re: [PATCH] zram: add zstd to the supported algorithms list

On Thu, Aug 24, 2017 at 09:33:54PM +, Nick Terrell wrote: > On Thu, Aug 24, 2017 at 10:49:36AM +0900, Sergey Senozhatsky wrote: > > Add ZSTD to the list of supported compression algorithms. > > > > Official benchmarks [1]: > > Awesome! Let me know if you need anything from me. > Hello,

Re: [PATCH] mm/page_alloc: don't reserve ZONE_HIGHMEM for ZONE_MOVABLE request

On Thu, Aug 24, 2017 at 11:41:58AM +0200, Vlastimil Babka wrote: > On 08/24/2017 07:45 AM, js1...@gmail.com wrote: > > From: Joonsoo Kim <iamjoonsoo@lge.com> > > > > Freepage on ZONE_HIGHMEM doesn't work for kernel memory so it's not that > > important to r

Re: [PATCH] mm/page_alloc: don't reserve ZONE_HIGHMEM for ZONE_MOVABLE request

On Thu, Aug 24, 2017 at 11:41:58AM +0200, Vlastimil Babka wrote: > On 08/24/2017 07:45 AM, js1...@gmail.com wrote: > > From: Joonsoo Kim > > > > Freepage on ZONE_HIGHMEM doesn't work for kernel memory so it's not that > > important to reserve. When ZONE_MOVABLE

Re: [PATCH] mm/page_alloc: don't reserve ZONE_HIGHMEM for ZONE_MOVABLE request

On Thu, Aug 24, 2017 at 11:30:50AM +0200, Michal Hocko wrote: > On Thu 24-08-17 14:45:46, Joonsoo Kim wrote: > > From: Joonsoo Kim <iamjoonsoo@lge.com> > > > > Freepage on ZONE_HIGHMEM doesn't work for kernel memory so it's not that > > important to r

Re: [PATCH] mm/page_alloc: don't reserve ZONE_HIGHMEM for ZONE_MOVABLE request

On Thu, Aug 24, 2017 at 11:30:50AM +0200, Michal Hocko wrote: > On Thu 24-08-17 14:45:46, Joonsoo Kim wrote: > > From: Joonsoo Kim > > > > Freepage on ZONE_HIGHMEM doesn't work for kernel memory so it's not that > > important to reserve. When ZONE_MOVABLE

Re: [PATCH] mm/mlock: use page_zone() instead of page_zone_id()

On Thu, Aug 24, 2017 at 01:05:15PM +0200, Vlastimil Babka wrote: > +CC Mel > > On 08/24/2017 09:20 AM, js1...@gmail.com wrote: > > From: Joonsoo Kim <iamjoonsoo@lge.com> > > > > page_zone_id() is a specialized function to compare the zone for the pages >

Re: [PATCH] mm/mlock: use page_zone() instead of page_zone_id()

On Thu, Aug 24, 2017 at 01:05:15PM +0200, Vlastimil Babka wrote: > +CC Mel > > On 08/24/2017 09:20 AM, js1...@gmail.com wrote: > > From: Joonsoo Kim > > > > page_zone_id() is a specialized function to compare the zone for the pages > > that are within

Re: "mm: use early_pfn_to_nid in page_ext_init" broken on some configurations?

On Mon, Jul 03, 2017 at 04:18:01PM +0200, Vlastimil Babka wrote: > On 07/03/2017 01:48 PM, Vlastimil Babka wrote: > > On 06/30/2017 04:18 PM, Michal Hocko wrote: > >> fe53ca54270a ("mm: use early_pfn_to_nid in page_ext_init") seem > >> to silently depend on CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID resp.

Re: "mm: use early_pfn_to_nid in page_ext_init" broken on some configurations?

On Mon, Jul 03, 2017 at 04:18:01PM +0200, Vlastimil Babka wrote: > On 07/03/2017 01:48 PM, Vlastimil Babka wrote: > > On 06/30/2017 04:18 PM, Michal Hocko wrote: > >> fe53ca54270a ("mm: use early_pfn_to_nid in page_ext_init") seem > >> to silently depend on CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID resp.

Re: "mm: use early_pfn_to_nid in page_ext_init" broken on some configurations?

On Mon, Jul 03, 2017 at 01:48:05PM +0200, Vlastimil Babka wrote: > On 06/30/2017 04:18 PM, Michal Hocko wrote: > > fe53ca54270a ("mm: use early_pfn_to_nid in page_ext_init") seem > > to silently depend on CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID resp. > > CONFIG_HAVE_MEMBLOCK_NODE_MAP. early_pfn_to_nid

Re: "mm: use early_pfn_to_nid in page_ext_init" broken on some configurations?

On Mon, Jul 03, 2017 at 01:48:05PM +0200, Vlastimil Babka wrote: > On 06/30/2017 04:18 PM, Michal Hocko wrote: > > fe53ca54270a ("mm: use early_pfn_to_nid in page_ext_init") seem > > to silently depend on CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID resp. > > CONFIG_HAVE_MEMBLOCK_NODE_MAP. early_pfn_to_nid

Re: "mm: use early_pfn_to_nid in page_ext_init" broken on some configurations?

On Fri, Jun 30, 2017 at 05:44:16PM +0200, Michal Hocko wrote: > On Fri 30-06-17 17:42:24, Michal Hocko wrote: > [...] > > diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h > > index 16532fa0bb64..894697c1e6f5 100644 > > --- a/include/linux/mmzone.h > > +++ b/include/linux/mmzone.h > >

Re: "mm: use early_pfn_to_nid in page_ext_init" broken on some configurations?

On Fri, Jun 30, 2017 at 05:44:16PM +0200, Michal Hocko wrote: > On Fri 30-06-17 17:42:24, Michal Hocko wrote: > [...] > > diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h > > index 16532fa0bb64..894697c1e6f5 100644 > > --- a/include/linux/mmzone.h > > +++ b/include/linux/mmzone.h > >

Re: [PATCH 2/2] mm, memory_hotplug: remove zone restrictions

llows only offline > nodes already. The original default_zone_for_pfn will become > default_kernel_zone_for_pfn. New default_zone_for_pfn implements the > above semantic. zone_for_pfn_range is slightly reorganized to implement > kernel and movable online type explicitly and MMOP_ONLINE_KEEP becomes > a catch all default behavior. > > Signed-off-by: Michal Hocko <mho...@suse.com> I appreaciate your help! Acked-by: Joonsoo Kim <iamjoonsoo@lge.com> Thanks.

Re: [PATCH 2/2] mm, memory_hotplug: remove zone restrictions

ine > nodes already. The original default_zone_for_pfn will become > default_kernel_zone_for_pfn. New default_zone_for_pfn implements the > above semantic. zone_for_pfn_range is slightly reorganized to implement > kernel and movable online type explicitly and MMOP_ONLINE_KEEP becomes > a catch all default behavior. > > Signed-off-by: Michal Hocko I appreaciate your help! Acked-by: Joonsoo Kim Thanks.

Re: [PATCH 1/2] mm, memory_hotplug: display allowed zones in the preferred ordering

ault online zone is not > duplicated. > > Signed-off-by: Michal Hocko <mho...@suse.com> > Acked-by: Joonsoo Kim <iamjoonsoo@lge.com> Thanks.

Re: [PATCH 1/2] mm, memory_hotplug: display allowed zones in the preferred ordering

nline into. > > Implementation is really simple. Pull out zone selection out of > move_pfn_range into zone_for_pfn_range helper and use it in > show_valid_zones to display the zone for default onlining and then > both kernel and movable if they are allowed. Default online zone is not > duplicated. > > Signed-off-by: Michal Hocko > Acked-by: Joonsoo Kim Thanks.

Re: [RFC][PATCH] slub: Introduce 'alternate' per cpu partial lists

d-off-by: Laura Abbott <labb...@redhat.com> > --- > This is a follow up to my previous proposal to speed up slub_debug=P > https://marc.info/?l=linux-mm=145920558822958=2 . The current approach > is hopelessly slow and can't really be used outside of limited debugging. > The goal is to

Re: [RFC][PATCH] slub: Introduce 'alternate' per cpu partial lists

Laura Abbott > --- > This is a follow up to my previous proposal to speed up slub_debug=P > https://marc.info/?l=linux-mm=145920558822958=2 . The current approach > is hopelessly slow and can't really be used outside of limited debugging. > The goal is to make slub_debug=P more usa

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

On Tue, Jun 13, 2017 at 07:49:47PM +0300, Andrey Ryabinin wrote: > On 06/08/2017 05:40 AM, Joonsoo Kim wrote: > >>> > >>> I don't understand why we trying to invent some hacky/complex schemes > >>> when we already have > >>> a simple one - scalin

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

On Tue, Jun 13, 2017 at 07:49:47PM +0300, Andrey Ryabinin wrote: > On 06/08/2017 05:40 AM, Joonsoo Kim wrote: > >>> > >>> I don't understand why we trying to invent some hacky/complex schemes > >>> when we already have > >>> a simple one - scalin

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

On Wed, May 31, 2017 at 07:31:53PM +0300, Andrey Ryabinin wrote: > On 05/31/2017 08:50 AM, Joonsoo Kim wrote: > >>> But the main win as I see it is that that's basically complete support > >>> for 32-bit arches. People do ask about arm32 support: > >>> ht

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

On Wed, May 31, 2017 at 07:31:53PM +0300, Andrey Ryabinin wrote: > On 05/31/2017 08:50 AM, Joonsoo Kim wrote: > >>> But the main win as I see it is that that's basically complete support > >>> for 32-bit arches. People do ask about arm32 support: > >>> ht

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

On Thu, Jun 01, 2017 at 08:06:02PM +0200, Dmitry Vyukov wrote: > On Tue, May 30, 2017 at 4:16 PM, Andrey Ryabinin > wrote: > > On 05/29/2017 06:29 PM, Dmitry Vyukov wrote: > >> Joonsoo, > >> > >> I guess mine (and Andrey's) main concern is the amount of additional > >>

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

On Thu, Jun 01, 2017 at 08:06:02PM +0200, Dmitry Vyukov wrote: > On Tue, May 30, 2017 at 4:16 PM, Andrey Ryabinin > wrote: > > On 05/29/2017 06:29 PM, Dmitry Vyukov wrote: > >> Joonsoo, > >> > >> I guess mine (and Andrey's) main concern is the amount of additional > >> complexity (I am still

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

On Tue, May 30, 2017 at 05:16:56PM +0300, Andrey Ryabinin wrote: > On 05/29/2017 06:29 PM, Dmitry Vyukov wrote: > > Joonsoo, > > > > I guess mine (and Andrey's) main concern is the amount of additional > > complexity (I am still struggling to understand how it all works) and > > more

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

On Tue, May 30, 2017 at 05:16:56PM +0300, Andrey Ryabinin wrote: > On 05/29/2017 06:29 PM, Dmitry Vyukov wrote: > > Joonsoo, > > > > I guess mine (and Andrey's) main concern is the amount of additional > > complexity (I am still struggling to understand how it all works) and > > more

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

On Wed, May 24, 2017 at 06:31:04PM +0200, Dmitry Vyukov wrote: > On Wed, May 24, 2017 at 8:04 AM, Joonsoo Kim <js1...@gmail.com> wrote: > >> >> > From: Joonsoo Kim <iamjoonsoo@lge.com> > >> >> > > >> >> > Hello, all. > &g

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

On Wed, May 24, 2017 at 06:31:04PM +0200, Dmitry Vyukov wrote: > On Wed, May 24, 2017 at 8:04 AM, Joonsoo Kim wrote: > >> >> > From: Joonsoo Kim > >> >> > > >> >> > Hello, all. > >> >> > > >> >>

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

On Wed, May 24, 2017 at 07:19:50PM +0200, Dmitry Vyukov wrote: > On Wed, May 24, 2017 at 9:45 AM, Joonsoo Kim <js1...@gmail.com> wrote: > >> > What does make your current patch work then? > >> > Say we map a new shadow page, update the page shadow to say t

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

On Wed, May 24, 2017 at 07:19:50PM +0200, Dmitry Vyukov wrote: > On Wed, May 24, 2017 at 9:45 AM, Joonsoo Kim wrote: > >> > What does make your current patch work then? > >> > Say we map a new shadow page, update the page shadow to say that there > >> > i

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

On Wed, May 24, 2017 at 08:57:23AM +0200, Dmitry Vyukov wrote: > On Tue, May 16, 2017 at 10:49 PM, Dmitry Vyukov <dvyu...@google.com> wrote: > > On Mon, May 15, 2017 at 11:23 PM, Joonsoo Kim <js1...@gmail.com> wrote: > >>> > > >>> > Hello, all.

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

On Wed, May 24, 2017 at 08:57:23AM +0200, Dmitry Vyukov wrote: > On Tue, May 16, 2017 at 10:49 PM, Dmitry Vyukov wrote: > > On Mon, May 15, 2017 at 11:23 PM, Joonsoo Kim wrote: > >>> > > >>> > Hello, all. > >>> > > >>> >

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

On Mon, May 22, 2017 at 05:00:29PM +0300, Andrey Ryabinin wrote: > > > On 05/19/2017 04:53 AM, Joonsoo Kim wrote: > > On Wed, May 17, 2017 at 03:17:13PM +0300, Andrey Ryabinin wrote: > >> On 05/16/2017 04:16 AM, js1...@gmail.com wrote: > >>> From:

Re: [PATCH v1 00/11] mm/kasan: support per-page shadow memory to reduce memory consumption

On Mon, May 22, 2017 at 05:00:29PM +0300, Andrey Ryabinin wrote: > > > On 05/19/2017 04:53 AM, Joonsoo Kim wrote: > > On Wed, May 17, 2017 at 03:17:13PM +0300, Andrey Ryabinin wrote: > >> On 05/16/2017 04:16 AM, js1...@gmail.com wrote: > >>> From:

<    1   2   3   4   5   6   7   8   9   10   >