linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Junxiao Bi <junxiao.bi@oracle.com>
To: Dave Chinner <david@fromorbit.com>,
	"Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	viro@zeniv.linux.org.uk, linux-mm@kvack.org
Subject: Re: [PATCH] vfs: stop shrinker while fs is freezed
Date: Mon, 16 Dec 2019 10:56:53 -0800	[thread overview]
Message-ID: <18e4b8ca-13d6-4c37-7248-006a0bab19d7@oracle.com> (raw)
In-Reply-To: <20191216041128.GK19213@dread.disaster.area>

[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]


On 12/15/19 8:11 PM, Dave Chinner wrote:
>>> diff --git a/fs/super.c b/fs/super.c
>>> index cfadab2cbf35..adc18652302b 100644
>>> --- a/fs/super.c
>>> +++ b/fs/super.c
>>> @@ -80,6 +80,11 @@ static unsigned long super_cache_scan(struct shrinker *shrink,
>>>   	if (!trylock_super(sb))
>>>   		return SHRINK_STOP;
>>>   
>>> +	if (sb->s_writers.frozen != SB_UNFROZEN) {
>>> +		up_read(&sb->s_umount);
>>> +		return SHRINK_STOP;
>>> +	}
>> Whatever happened to "let's just fsfreeze the filesystems shortly before
>> freezing the system?  Did someone find a reason why that wouldn't work?
>>
>> Also, uh, doesn't this disable memory reclaim for frozen filesystems?
>>
>> Maybe we all need to go review the xfs io-less inode reclaim series so
>> we can stop running transactions in reclaim... I can't merge any of it
>> until the mm changes go upstream.
> IO-less reclaim doesn't prevent ->destroy_inode from having to run
> transactions. e.g. this is the path through which unlink does inode
> freeing. Background inode inactivation is the patchset that
> addresses this problem...:)

Sound backgroup inode inactivation is only for xfs? I suppose this is a 
generic issue, other fs will also suffer this?

Thanks,

Junxiao.

>
> Cheers,
>
> Dave.

[-- Attachment #2: Type: text/html, Size: 2117 bytes --]

      reply	other threads:[~2019-12-16 18:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191213222440.11519-1-junxiao.bi@oracle.com>
2019-12-14  0:40 ` Darrick J. Wong
2019-12-16  4:11   ` Dave Chinner
2019-12-16 18:56     ` Junxiao Bi [this message]

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=18e4b8ca-13d6-4c37-7248-006a0bab19d7@oracle.com \
    --to=junxiao.bi@oracle.com \
    --cc=darrick.wong@oracle.com \
    --cc=david@fromorbit.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=viro@zeniv.linux.org.uk \
    /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