From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: junxiao.bi@oracle.com
Cc: Song Liu <song@kernel.org>, 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: Fri, 17 Nov 2023 09:36:40 +0100 [thread overview]
Message-ID: <20231117093640.00006b70@linux.intel.com> (raw)
In-Reply-To: <c13b580b-434f-4a4b-b0b4-917f8b042de3@oracle.com>
On Thu, 16 Nov 2023 09:04:34 -0800
junxiao.bi@oracle.com wrote:
> On 11/15/23 7:30 AM, Mariusz Tkaczyk wrote:
>
> > 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.
> Agree, sound like that's the way to proceed.
> >
> > 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?
>
> Unfortunately that's is not possible, it's a production setup to use
> imsm raid.
Implementing IMSM in kernel is a goal for months/ years so I don't
see it in a timeline you would need that on to fix your production setup. It
will be a big feature, but let's wait for Song voice first.
Thanks,
Mariusz
prev parent reply other threads:[~2023-11-17 8:36 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
2023-11-16 17:04 ` junxiao.bi
2023-11-17 8:36 ` Mariusz Tkaczyk [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=20231117093640.00006b70@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