From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: junxiao.bi@oracle.com, Song Liu <song@kernel.org>
Cc: Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
gregkh@linuxfoundation.org
Subject: Re: [PATCH] kernfs: support kernfs notify in memory recliam context
Date: Wed, 15 Nov 2023 16:30:51 +0100 [thread overview]
Message-ID: <20231115162915.000064f8@linux.intel.com> (raw)
In-Reply-To: <443775e1-ed94-452e-8f06-eadb777bede4@oracle.com>
On Tue, 14 Nov 2023 15:53:47 -0800
junxiao.bi@oracle.com wrote:
> Understood, thanks. Sound like depending on Userspace on memory reclaim
> path is really bad idea and the only option for fixing it is to remove
> that dependency, but i am not sure that is possible without breaking the
> consistency of metadata.
>
> Thanks,
>
> Junxiao.
Indeed the project of external metadata management if fragile. You cares about
IMSM here (same as me) so ideally we should implement metadata management in
kernel- I think that IMSM deserved that after 10 years on the market. There is
no better option, other options are just "workarounds" for the lack of metadata
management in kernel.
Song, any comments here?
From the second hand, there is native raid which should just work, so maybe you
can switch to the native raid?
Thanks,
Mariusz
next prev parent reply other threads:[~2023-11-15 15:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 18:59 [PATCH] kernfs: support kernfs notify in memory recliam context Junxiao Bi
2023-11-14 19:06 ` Tejun Heo
2023-11-14 20:09 ` junxiao.bi
2023-11-14 20:24 ` Tejun Heo
2023-11-14 23:53 ` junxiao.bi
2023-11-15 15:30 ` Mariusz Tkaczyk [this message]
2023-11-16 17:04 ` junxiao.bi
2023-11-17 8:36 ` Mariusz Tkaczyk
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=20231115162915.000064f8@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=junxiao.bi@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=song@kernel.org \
--cc=tj@kernel.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