From: santosh.shilimkar@oracle.com
To: Nishanth Menon <nm@ti.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Tero Kristo <t-kristo@ti.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Michal Hocko <mhocko@suse.com>, Rik van Riel <riel@surriel.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Dave Chinner <david@fromorbit.com>,
Russell King - ARM Linux admin <linux@armlinux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>, Yafang Shao <laoar.shao@gmail.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
kernel-team@fb.com, Kishon Vijay Abraham I <kishon@ti.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Roman Gushchin <guro@fb.com>
Subject: Re: [PATCH] vfs: keep inodes with page cache off the inode shrinker LRU
Date: Fri, 6 Mar 2020 17:08:03 -0800 [thread overview]
Message-ID: <7b179d51-3d08-53f5-9b6e-552869f8ed78@oracle.com> (raw)
In-Reply-To: <20200306203439.peytghdqragjfhdx@kahuna>
On 3/6/20 12:34 PM, Nishanth Menon wrote:
> On 13:11-20200226, santosh.shilimkar@oracle.com wrote:
>> +Nishant, Tero
>>
>> On 2/26/20 1:01 PM, Arnd Bergmann wrote:
>>> On Wed, Feb 26, 2020 at 7:04 PM <santosh.shilimkar@oracle.com> wrote:
>>>>
>>>> On 2/13/20 8:52 AM, Arnd Bergmann wrote:
>>>>> On Wed, Feb 12, 2020 at 9:50 AM Russell King - ARM Linux admin
>>>>> <linux@armlinux.org.uk> wrote:
>>>>
>>>> The Keystone generations of SOCs have been used in different areas and
>>>> they will be used for long unless says otherwise.
>>>>
>>>> Apart from just split of lowmem and highmem, one of the peculiar thing
>>>> with Keystome family of SOCs is the DDR is addressable from two
>>>> addressing ranges. The lowmem address range is actually non-cached
>>>> range and the higher range is the cacheable.
>>>
>>> I'm aware of Keystone's special physical memory layout, but for the
>>> discussion here, this is actually irrelevant for the discussion about
>>> highmem here, which is only about the way we map all or part of the
>>> available physical memory into the 4GB of virtual address space.
>>>
>>> The far more important question is how much memory any users
>>> (in particular the subset that are going to update their kernels
>>> several years from now) actually have installed. Keystone-II is
>>> one of the rare 32-bit chips with fairly wide memory interfaces,
>>> having two 72-bit (with ECC) channels rather than the usual one
>>> or two channels of 32-bit DDR3. This means a relatively cheap
>>> 4GB configuration using eight 256Mx16 chips is possible, or
>>> even a 8GB using sixteen or eighteen 512Mx8.
>>>
>>> Do you have an estimate on how common these 4GB and 8GB
>>> configurations are in practice outside of the TI evaluation
>>> board?
>>>
>> From my TI memories, many K2 customers were going to install
>> more than 2G memory. Don't remember 8G, but 4G was the dominant
>> one afair. Will let Nishant/Tero elaborate latest on this.
>>
>
> Thanks for the headsup, it took a little to dig up the current
> situation:
>
> ~few 1000s still relevant spread between 4G and 8G (confirmed that both
> are present, relevant and in use).
>
> I wish we could sunset, but unfortunately, I am told(and agree)
> that we should'nt just leave products (and these are long term
> products stuck in critical parts in our world) hanging in the air, and
> migrations to newer kernel do still take place periodically (the best
> I can talk in public forum at least).
>
Thanks Nishant !!
next prev parent reply other threads:[~2020-03-07 1:09 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 17:55 [PATCH] vfs: keep inodes with page cache off the inode shrinker LRU Johannes Weiner
2020-02-11 18:20 ` Johannes Weiner
2020-02-11 19:05 ` Rik van Riel
2020-02-11 19:31 ` Johannes Weiner
2020-02-11 23:44 ` Andrew Morton
2020-02-12 0:28 ` Linus Torvalds
2020-02-12 0:47 ` Andrew Morton
2020-02-12 1:03 ` Linus Torvalds
2020-02-12 8:50 ` Russell King - ARM Linux admin
2020-02-13 9:50 ` Lucas Stach
2020-02-13 16:52 ` Arnd Bergmann
2020-02-15 11:25 ` Geert Uytterhoeven
2020-02-15 16:59 ` Arnd Bergmann
2020-02-16 9:44 ` Geert Uytterhoeven
2020-02-16 19:54 ` Chris Paterson
2020-02-16 20:38 ` Arnd Bergmann
2020-02-20 14:35 ` Chris Paterson
2020-02-26 18:04 ` santosh.shilimkar
2020-02-26 21:01 ` Arnd Bergmann
2020-02-26 21:11 ` santosh.shilimkar
2020-03-06 20:34 ` Nishanth Menon
2020-03-07 1:08 ` santosh.shilimkar [this message]
2020-03-08 10:58 ` Arnd Bergmann
2020-03-08 14:19 ` Russell King - ARM Linux admin
2020-03-09 13:33 ` Arnd Bergmann
2020-03-09 14:04 ` Russell King - ARM Linux admin
2020-03-09 15:04 ` Arnd Bergmann
2020-03-10 9:16 ` Michal Hocko
2020-03-09 15:59 ` Catalin Marinas
2020-03-09 16:09 ` Russell King - ARM Linux admin
2020-03-09 16:57 ` Catalin Marinas
2020-03-09 19:46 ` Arnd Bergmann
2020-03-11 14:29 ` Catalin Marinas
2020-03-11 16:59 ` Arnd Bergmann
2020-03-11 17:26 ` Catalin Marinas
2020-03-11 22:21 ` Arnd Bergmann
2020-02-12 3:58 ` Matthew Wilcox
2020-02-12 8:09 ` Michal Hocko
2020-02-17 13:31 ` Pavel Machek
2020-02-12 16:35 ` Johannes Weiner
2020-02-12 18:26 ` Andrew Morton
2020-02-12 18:52 ` Johannes Weiner
2020-02-12 12:25 ` Yafang Shao
2020-02-12 16:42 ` Johannes Weiner
2020-02-13 1:47 ` Yafang Shao
2020-02-13 13:46 ` Johannes Weiner
2020-02-14 2:02 ` Yafang Shao
2020-02-13 18:34 ` [PATCH v2] " Johannes Weiner
2020-02-14 16:53 ` [PATCH] " kbuild test robot
2020-02-14 21:30 ` kbuild test robot
2020-02-14 21:30 ` [PATCH] vfs: fix boolreturn.cocci warnings kbuild test robot
2020-05-12 21:29 ` [PATCH] vfs: keep inodes with page cache off the inode shrinker LRU Johannes Weiner
2020-05-13 1:32 ` Yafang Shao
2020-05-13 13:00 ` Johannes Weiner
2020-05-13 21:15 ` Andrew Morton
2020-05-14 11:27 ` Johannes Weiner
2020-05-14 2:24 ` Andrew Morton
2020-05-14 10:37 ` Johannes Weiner
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=7b179d51-3d08-53f5-9b6e-552869f8ed78@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=david@fromorbit.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=kishon@ti.com \
--cc=laoar.shao@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@armlinux.org.uk \
--cc=mhocko@suse.com \
--cc=nm@ti.com \
--cc=riel@surriel.com \
--cc=ssantosh@kernel.org \
--cc=t-kristo@ti.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).