From: Mike Galbraith <efault@gmx.de>
To: Sergey Senozhatsky <senozhatsky@chromium.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Jens Axboe <axboe@kernel.dk>, Minchan Kim <minchan@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] zram: Replace bit spinlocks with spinlock_t for PREEMPT_RT.
Date: Fri, 24 Mar 2023 05:32:49 +0100 [thread overview]
Message-ID: <b990dfaa093d8a3b219a789c7ebf972bf001772b.camel@gmx.de> (raw)
In-Reply-To: <20230324040750.GE3271889@google.com>
On Fri, 2023-03-24 at 13:07 +0900, Sergey Senozhatsky wrote:
> On (23/03/23 17:18), Sebastian Andrzej Siewior wrote:
> > Mike most likely stumbled upon it while running LTP.
>
> Yeah, I'm curious if anyone uses zram in preempt-rt systems. I don't
> mind this patch but would be nice to add new code when it solves some
> real problems. Maybe `depend on !PREEMPT_RT` can be a better option.
Patchlet's job here is only obese config RT vs !RT testing. It can
always move back into local_patches, it won't be lonely ;-)
-Mike
next prev parent reply other threads:[~2023-03-24 4:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 16:18 [PATCH] zram: Replace bit spinlocks with spinlock_t for PREEMPT_RT Sebastian Andrzej Siewior
2023-03-24 4:07 ` Sergey Senozhatsky
2023-03-24 4:32 ` Mike Galbraith [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-19 15:08 Sebastian Andrzej Siewior
2024-06-19 17:34 ` Jens Axboe
2024-06-19 17:52 ` Sebastian Andrzej Siewior
2024-06-19 18:01 ` Jens Axboe
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=b990dfaa093d8a3b219a789c7ebf972bf001772b.camel@gmx.de \
--to=efault@gmx.de \
--cc=axboe@kernel.dk \
--cc=bigeasy@linutronix.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=senozhatsky@chromium.org \
--cc=tglx@linutronix.de \
/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