From: Michael Ellerman <mpe@ellerman.id.au>
To: Jens Axboe <axboe@kernel.dk>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Nicholas Piggin <npiggin@gmail.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Memory coherency issue with IO thread offloading?
Date: Sat, 25 Mar 2023 11:15:16 +1100 [thread overview]
Message-ID: <87jzz5u1nv.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <5fa06524-7170-aeb4-4b5c-2be2ffad696b@kernel.dk>
Jens Axboe <axboe@kernel.dk> writes:
> On 3/24/23 1:27?AM, Christophe Leroy wrote:
>> Le 23/03/2023 ? 19:54, Jens Axboe a ?crit :
>>> I got a report sent to me from mariadb, in where 5.10.158 works fine and
>>> 5.10.162 is broken. And in fact, current 6.3-rc also fails the test
>>> case. Beware that this email is long, as I'm trying to include
>>> everything that may be relevant...
>>
>> Which variant of powerpc ? 32 or 64 bits ? Book3S or BookE ?
>
> I knew I'd forget something important... It's power9:
>
> processor : 0
> cpu : POWER9 (architected), altivec supported
> clock : 2200.000000MHz
> revision : 2.2 (pvr 004e 1202)
Believe it or not there's still more variables in play, Power9 has two
different MMUs, and Linux can run on two different hypervisors as well
as on bare metal P9 :)
Can you paste the last ~10 lines of /proc/cpuinfo, with the "machine",
"firmware" and "MMU" lines, that should tell us everything we need to
know.
cheers
next prev parent reply other threads:[~2023-03-25 0:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 18:54 Memory coherency issue with IO thread offloading? Jens Axboe
2023-03-24 7:27 ` Christophe Leroy
2023-03-24 12:06 ` Jens Axboe
2023-03-25 0:15 ` Michael Ellerman [this message]
2023-03-25 0:20 ` Jens Axboe
2023-03-25 0:42 ` Michael Ellerman
2023-03-25 1:15 ` Jens Axboe
2023-03-25 1:20 ` Jens Axboe
2023-03-27 4:22 ` Nicholas Piggin
2023-03-27 12:39 ` Jens Axboe
2023-03-27 21:24 ` Jens Axboe
2023-03-28 12:51 ` Michael Ellerman
2023-03-28 16:38 ` Jens Axboe
2023-03-27 13:53 ` Michael Ellerman
2023-03-28 6:20 Daniel Black
2023-03-28 12:10 ` Michael Ellerman
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=87jzz5u1nv.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=axboe@kernel.dk \
--cc=christophe.leroy@csgroup.eu \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).