linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Daniel Black <daniel@mariadb.org>, linuxppc-dev@lists.ozlabs.org
Subject: Re: Memory coherency issue with IO thread offloading?
Date: Tue, 28 Mar 2023 23:10:55 +1100	[thread overview]
Message-ID: <87cz4tcbzk.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <CABVffEN2=G3nFyk12qwWwtk6ZZiXoNquXUJ_oYTKa0q2=GE76Q@mail.gmail.com>

Daniel Black <daniel@mariadb.org> writes:
> Thanks Jens, Nick, Christophe and Michael for your work so far.
>
> Apologies for the out of thread email.
>
> Confirming MariabD-10.6+ is required( when we added liburing), and
> previous versions used libaio (which tested without incident as mpe
> retested).

Thanks! I was trying to follow the threads from the mariadb/server
github to find the CI but didn't have much luck. No .travis.yml these
days :)

> We were (we're now back on the old good kernel Jens indicated) getting
> failures like https://buildbot.mariadb.org/#/builders/231/builds/16857
> in a container (of various distro userspaces) on bare metal.
>
> bare metal end of /proc/cpuinfo
>
> processor    : 127
> cpu        : POWER9, altivec supported
> clock        : 3283.000000MHz
> revision    : 2.2 (pvr 004e 1202)
>
> timebase    : 512000000
> platform    : PowerNV
> model        : 9006-22P
> machine        : PowerNV 9006-22P
> firmware    : OPAL
> MMU        : Radix

Thanks, looks like that's a Boston, which at least has the same CPU as
the machine I'm testing on.

I have also reproduced it on bare metal now, but it seems much easier to
hit it in an LPAR (on P10). Not sure that's an actual data point, could
just be due to other activity on the box.

cheers

  reply	other threads:[~2023-03-28 12:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28  6:20 Memory coherency issue with IO thread offloading? Daniel Black
2023-03-28 12:10 ` Michael Ellerman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-03-23 18:54 Jens Axboe
2023-03-24  7:27 ` Christophe Leroy
2023-03-24 12:06   ` Jens Axboe
2023-03-25  0:15     ` Michael Ellerman
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

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=87cz4tcbzk.fsf@mpe.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=daniel@mariadb.org \
    --cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).