lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20231217214656.ee095a1df467b745ad1ca75e@linux-foundation.org>
Date: Sun, 17 Dec 2023 21:46:56 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Matthew Wilcox <willy@...radead.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Yu Zhao
 <yuzhao@...gle.com>, linux-mm@...ck.org, linux-kernel@...r.kernel.org,
 Jesse Barnes <jsbarnes@...gle.com>, Suren Baghdasaryan <surenb@...gle.com>,
 Guru Anbalagane <gurua@...gle.com>, David Rientjes <rientjes@...gle.com>
Subject: Re: [GIT PULL] hotfixes for 6.7-rc6

On Sun, 17 Dec 2023 15:40:19 +0000 Matthew Wilcox <willy@...radead.org> wrote:

> On Sat, Dec 16, 2023 at 04:16:45PM -0800, Linus Torvalds wrote:
> > On Fri, 15 Dec 2023 at 20:57, Yu Zhao <yuzhao@...gle.com> wrote:
> > >
> > > There has been a short-term plan, i.e., moving some of folio->flags to
> > > the lower bits of folio->lru so that we can drop the Kconfig
> > > constraint. I have discussed this with Willy but never acted on it. My
> > > priority has been to surface more of our ideas that can potentially
> > > save users money on memory to the community. I'm CC'ing our team
> > > leads. Please feel free to let us know your preference on the
> > > priority.
> > 
> > This is definitely a "eventually" thing on my wishlist, so I was more
> > just wanting to hear that there is a plan, and somebody working on
> > it..
> 
> "eventually" we should get rid of LRUs altogether.  They're no good for
> a modern CPU.
> 
> https://lore.kernel.org/linux-mm/ZTc7SHQ4RbPkD3eZ@casper.infradead.org/
> 

OK, but...

What of the cost of physical I/O?  If a computationally more expensive
scan results in less I/O (hopefully) then the balance is altered?


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ