From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Gregory Price <gregory.price@memverge.com>
Cc: Yuquan Wang <wangyuquan1236@phytium.com.cn>,
<dan.j.williams@intel.com>, <dimitrios.palyvos@zptcorp.com>,
<linux-cxl@vger.kernel.org>
Subject: Re: Questions about the memory of CXL Type3 device offline
Date: Wed, 11 Oct 2023 15:06:20 +0100 [thread overview]
Message-ID: <20231011150620.0000212a@Huawei.com> (raw)
In-Reply-To: <ZSKu+bZfQmuTkrDH@memverge.com>
On Sun, 8 Oct 2023 09:30:33 -0400
Gregory Price <gregory.price@memverge.com> wrote:
> On Tue, Oct 10, 2023 at 02:46:48PM +0800, Yuquan Wang wrote:
> > On 2023-10-07 18:56, gregory.price@memverge.com wrote:
> > > because you likely have auto-online of new memory blocks sets to false.
> > >
> > > use `daxctl list` and `daxctl online-memory [dax-device]` to online the memory
> >
> > Thank you Gregory. It works! :)
> >
> > BTW, I aslo did the same test in 'virt'(arm64) on Jonathan's development branch,
> > however, it would automatically allcate CXL memory to numa node 0:
> >
>
> I haven't done any work with the arm machine. Jonathan might have
> input.
>
> But if the memory comes up, it's probably fine. If the memory comes up
> automatically it's because you have auto-online turned on.
ARMs management of numa nodes is a bit simplistic currently as it doesn't
keep as much information around as x86 does. That's something I've been
meaning to fix (in kernel) but not done so yet.
J
>
> ~Gregory
next prev parent reply other threads:[~2023-10-11 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 6:46 Questions about the memory of CXL Type3 device offline Yuquan Wang
2023-10-08 13:30 ` Gregory Price
2023-10-11 14:06 ` Jonathan Cameron [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-09 12:39 Yuquan Wang
2023-10-07 10:56 ` Gregory Price
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=20231011150620.0000212a@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=dimitrios.palyvos@zptcorp.com \
--cc=gregory.price@memverge.com \
--cc=linux-cxl@vger.kernel.org \
--cc=wangyuquan1236@phytium.com.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.