linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Yafang Shao <laoar.shao@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Dave Chinner <david@fromorbit.com>,
	Christoph Hellwig <hch@infradead.org>,
	 "Darrick J. Wong" <darrick.wong@oracle.com>,
	Michal Hocko <mhocko@kernel.org>,
	 Andrew Morton <akpm@linux-foundation.org>,
	linux-xfs@vger.kernel.org,  linux-fsdevel@vger.kernel.org,
	Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH v5 1/2] mm: Add become_kswapd and restore_kswapd
Date: Wed, 19 Aug 2020 13:49:35 +0800	[thread overview]
Message-ID: <CALOAHbBoJbKJ82iPzBumqSm81fUmrJkP_+wPiA+A5dJiD24cdA@mail.gmail.com> (raw)
In-Reply-To: <20200819030852.GX17456@casper.infradead.org>

On Wed, Aug 19, 2020 at 11:08 AM Matthew Wilcox <willy@infradead.org> wrote:
>
> On Wed, Aug 19, 2020 at 10:24:24AM +0800, Yafang Shao wrote:
> > From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
> >
> > Since XFS needs to pretend to be kswapd in some of its worker threads,
> > create methods to save & restore kswapd state.  Don't bother restoring
> > kswapd state in kswapd -- the only time we reach this code is when we're
> > exiting and the task_struct is about to be destroyed anyway.
> >
> > Cc: Dave Chinner <david@fromorbit.com>
> > Cc: Christoph Hellwig <hch@infradead.org>
> > Cc: Michal Hocko <mhocko@kernel.org>
> > Cc: Darrick J. Wong <darrick.wong@oracle.com>
> > Cc: Matthew Wilcox <willy@infradead.org>
> > Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> > Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
>
> See https://lore.kernel.org/linux-mm/20200625123143.GK1320@dhcp22.suse.cz/
>
> Please add:
>
> Acked-by: Michal Hocko <mhocko@suse.com>
>

Sure.
I missed that discussion.

> > +/*
> > + * Tell the memory management that we're a "memory allocator",
> > + * and that if we need more memory we should get access to it
> > + * regardless (see "__alloc_pages()"). "kswapd" should
> > + * never get caught in the normal page freeing logic.
> > + *
> > + * (Kswapd normally doesn't need memory anyway, but sometimes
> > + * you need a small amount of memory in order to be able to
> > + * page out something else, and this flag essentially protects
> > + * us from recursively trying to free more memory as we're
> > + * trying to free the first piece of memory in the first place).
> > + */
>
> And let's change that comment as suggested by Michal (slightly edited
> by me):
>
> /*
>  * Tell the memory management code that this thread is working on behalf
>  * of background memory reclaim (like kswapd).  That means that it will
>  * get access to memory reserves should it need to allocate memory in
>  * order to make forward progress.  With this great power comes great
>  * responsibility to not exhaust those reserves.
>  */
>

I will update it with that comment.

> > +#define KSWAPD_PF_FLAGS              (PF_MEMALLOC | PF_SWAPWRITE | PF_KSWAPD)
> > +
> > +static inline unsigned long become_kswapd(void)
> > +{
> > +     unsigned long flags = current->flags & KSWAPD_PF_FLAGS;
> > +
> > +     current->flags |= KSWAPD_PF_FLAGS;
> > +
> > +     return flags;
> > +}
> > +
> > +static inline void restore_kswapd(unsigned long flags)
> > +{
> > +     current->flags &= ~(flags ^ KSWAPD_PF_FLAGS);
> > +}
> > +
> >  #ifdef CONFIG_MEMCG
> >  /**
> >   * memalloc_use_memcg - Starts the remote memcg charging scope.
> > diff --git a/mm/vmscan.c b/mm/vmscan.c
> > index 99e1796eb833..3a2615bfde35 100644
> > --- a/mm/vmscan.c
> > +++ b/mm/vmscan.c
> > @@ -3859,19 +3859,7 @@ static int kswapd(void *p)
> >       if (!cpumask_empty(cpumask))
> >               set_cpus_allowed_ptr(tsk, cpumask);
> >
> > -     /*
> > -      * Tell the memory management that we're a "memory allocator",
> > -      * and that if we need more memory we should get access to it
> > -      * regardless (see "__alloc_pages()"). "kswapd" should
> > -      * never get caught in the normal page freeing logic.
> > -      *
> > -      * (Kswapd normally doesn't need memory anyway, but sometimes
> > -      * you need a small amount of memory in order to be able to
> > -      * page out something else, and this flag essentially protects
> > -      * us from recursively trying to free more memory as we're
> > -      * trying to free the first piece of memory in the first place).
> > -      */
> > -     tsk->flags |= PF_MEMALLOC | PF_SWAPWRITE | PF_KSWAPD;
> > +     become_kswapd();
> >       set_freezable();
> >
> >       WRITE_ONCE(pgdat->kswapd_order, 0);
> > @@ -3921,8 +3909,6 @@ static int kswapd(void *p)
> >                       goto kswapd_try_sleep;
> >       }
> >
> > -     tsk->flags &= ~(PF_MEMALLOC | PF_SWAPWRITE | PF_KSWAPD);
> > -
> >       return 0;
> >  }
> >
> > --
> > 2.18.1
> >



-- 
Thanks
Yafang


  reply	other threads:[~2020-08-19  5:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-19  2:24 [PATCH v5 0/2] avoid xfs transaction reservation recursion Yafang Shao
2020-08-19  2:24 ` [PATCH v5 1/2] mm: Add become_kswapd and restore_kswapd Yafang Shao
2020-08-19  3:08   ` Matthew Wilcox
2020-08-19  5:49     ` Yafang Shao [this message]
2020-08-19  2:24 ` [PATCH v5 2/2] xfs: avoid transaction reservation recursion Yafang Shao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALOAHbBoJbKJ82iPzBumqSm81fUmrJkP_+wPiA+A5dJiD24cdA@mail.gmail.com \
    --to=laoar.shao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mhocko@kernel.org \
    --cc=willy@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox