From: Pekka Enberg <penberg@gmail.com>
To: Cho KyongHo <pullip.cho@samsung.com>
Cc: David Hildenbrand <david@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
hyesoo.yu@samsung.com, janghyuck.kim@samsung.com
Subject: Re: [PATCH] mm: sort freelist by rank number
Date: Wed, 19 Aug 2020 16:12:32 +0300 [thread overview]
Message-ID: <CAOJsxLGP3MVhfehfs5pYsAUmc7CnHCmgBFN7E-1u8spfD3MymA@mail.gmail.com> (raw)
In-Reply-To: <20200818085444.GA72202@KEI>
Hi KyongHo and David,
On 07.08.20 09:08, Pekka Enberg wrote:
> > > I think having more knowledge of DRAM controller details in the OS
> > > would be potentially beneficial for better page allocation policy, so
> > > maybe try come up with something more generic, even if the fallback to
> > > providing this information is a kernel command line option.
On Tue, Aug 18, 2020 at 12:02 PM Cho KyongHo <pullip.cho@samsung.com> wrote:
> I don't find if there is a way to deliver detailed DRAM information
> through ACPI, ATAG or something similar. But I didn't find.
Perhaps that's still the case today then.
In the context of this patch, what I am hoping is that we'd turn the
"dram_rank_granule" parameter -- even if it's still a manually
configured thing -- into an abstraction that we can later extend. IOW,
something similar to what the "energy model"
(kernel/power/energy_model.c) today is.
On Mon, Aug 10, 2020 at 09:32:18AM +0200, David Hildenbrand wrote:
> I guess one universal approach is by measuring access times ... not what
> we might be looking for :)
I don't think it's an unreasonable approach, but measurement accuracy
and speed will determine if it's actually practical. There are
examples of this kind of approach elsewhere too. For example, MCTOP
[1] which aims to provide topology-aware OS abstractions, uses cache
latency measurements to infer the topology.
1. https://timharris.uk/papers/2017-eurosys-mctop.pdf
Regards,
- Pekka
prev parent reply other threads:[~2020-08-19 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200803061805epcas2p20faeeff0b31b23d1bc4464972285b561@epcas2p2.samsung.com>
2020-08-03 6:10 ` pullip.cho
2020-08-03 7:57 ` David Hildenbrand
2020-08-03 15:45 ` Vlastimil Babka
2020-08-04 2:35 ` Cho KyongHo
2020-08-04 9:12 ` Vlastimil Babka
2020-08-04 10:20 ` Cho KyongHo
2020-08-07 7:08 ` Pekka Enberg
2020-08-10 7:32 ` David Hildenbrand
2020-08-18 8:54 ` Cho KyongHo
2020-08-19 13:12 ` Pekka Enberg [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=CAOJsxLGP3MVhfehfs5pYsAUmc7CnHCmgBFN7E-1u8spfD3MymA@mail.gmail.com \
--to=penberg@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hyesoo.yu@samsung.com \
--cc=janghyuck.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pullip.cho@samsung.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