From: Vitaly Wool <vitaly.wool@konsulko.com>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: Linux-MM <linux-mm@kvack.org>,
lkml@vger.kernel.org, linux-rt-users@vger.kernel.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Mike Galbraith <efault@gmx.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/3] z3fold: stability / rt fixes
Date: Sat, 19 Dec 2020 00:26:56 +0100 [thread overview]
Message-ID: <CAM4kBBL=f4o+zvwqjfonoMEaJu9iBD_RL0uENXRe-XAOKB-PZg@mail.gmail.com> (raw)
In-Reply-To: <20201218231934.nwdj6zok2fndgexk@spock.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
Hi Oleksandr,
On Sat, 19 Dec 2020, 00:19 Oleksandr Natalenko, <oleksandr@natalenko.name>
wrote:
> On Wed, Dec 09, 2020 at 04:51:48PM +0200, Vitaly Wool wrote:
> > This patchset addresses z3fold stability issues under stress load,
> > primarily in the reclaim and free aspects. Besides, it fixes the
> > locking problems that were only seen in real-time kernel
> > configuration.
> >
> > Vitaly Wool (2):
> > z3fold: simplify freeing slots
> > z3fold: stricter locking and more careful reclaim
> >
> > Mike Galbraith (1):
> > z3fold: Remove preempt disabled sections for RT
> >
> > mm/z3fold.c | 191 ++++++++++++++++++++++++++--------------------------
> > 1 file changed, 96 insertions(+), 95 deletions(-)
> >
> > --
> > 2.20.1
> >
>
> Thanks for addressing this!
>
> (I'd appreciate Cc'ing me on this though since I was the one who
> reported it initially...)
>
I'm glad it helped. Leaving you off the explicit CC-list is surely
unintentional. In fact, I didn't know about the original issue, I was just
added by Sebastian to the ongoing conversation and so I believe I CC'd
everyone who took part in it.
Best regards,
Vitaly
> --
> Oleksandr Natalenko (post-factum)
>
[-- Attachment #2: Type: text/html, Size: 1953 bytes --]
prev parent reply other threads:[~2020-12-18 23:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 14:51 Vitaly Wool
2020-12-09 14:51 ` [PATCH 1/3] z3fold: simplify freeing slots Vitaly Wool
2020-12-09 14:51 ` [PATCH 2/3] z3fold: Remove preempt disabled sections for RT Vitaly Wool
2020-12-09 14:51 ` [PATCH 3/3] z3fold: stricter locking and more careful reclaim Vitaly Wool
2020-12-18 23:19 ` [PATCH 0/3] z3fold: stability / rt fixes Oleksandr Natalenko
2020-12-18 23:26 ` Vitaly Wool [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='CAM4kBBL=f4o+zvwqjfonoMEaJu9iBD_RL0uENXRe-XAOKB-PZg@mail.gmail.com' \
--to=vitaly.wool@konsulko.com \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=efault@gmx.de \
--cc=linux-mm@kvack.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=lkml@vger.kernel.org \
--cc=oleksandr@natalenko.name \
/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