[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+t-nXQwU7q_2jVM+PY16wETRp9tBngcpWMtSnBz1u1ev-ZBig@mail.gmail.com>
Date: Thu, 31 Jan 2019 09:46:48 -0800
From: Josh Snyder <joshs@...flix.com>
To: Michal Hocko <mhocko@...nel.org>
Cc: Vlastimil Babka <vbabka@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
open list <linux-kernel@...r.kernel.org>,
Linux-MM <linux-mm@...ck.org>,
Linux API <linux-api@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Greg KH <gregkh@...uxfoundation.org>,
Jann Horn <jannh@...gle.com>, Jiri Kosina <jkosina@...e.cz>,
Dominique Martinet <asmadeus@...ewreck.org>,
Andy Lutomirski <luto@...capital.net>,
Dave Chinner <david@...morbit.com>,
Kevin Easton <kevin@...rana.org>,
Matthew Wilcox <willy@...radead.org>,
Cyril Hrubis <chrubis@...e.cz>, Tejun Heo <tj@...nel.org>,
"Kirill A . Shutemov" <kirill@...temov.name>,
Daniel Gruss <daniel@...ss.cc>, Jiri Kosina <jikos@...nel.org>
Subject: Re: [PATCH 1/3] mm/mincore: make mincore() more conservative
On Thu, Jan 31, 2019 at 1:44 AM Michal Hocko <mhocko@...nel.org> wrote:
> One thing is still not clear to me though. Is the new owner/writeable
> check OK for the Netflix-like usecases? I mean does happycache have
> appropriate access to the cache data? I have tried to re-read the
> original thread but couldn't find any confirmation.
The owner/writable check will suit every database that I've ever used
happycache with, including cassandra, postgres and git.
Acked-by: Josh Snyder <joshs@...flix.com>
Powered by blists - more mailing lists