From: Jeff Moyer <jmoyer@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: Dan Williams <dan.j.williams@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-nvdimm@lists.01.org
Subject: Re: Problems with VM_MIXEDMAP removal from /proc/<pid>/smaps
Date: Tue, 16 Oct 2018 08:35:00 -0400 [thread overview]
Message-ID: <x49d0sahxxn.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20181016082540.GA18918@quack2.suse.cz> (Jan Kara's message of "Tue, 16 Oct 2018 10:25:40 +0200")
Jan Kara <jack@suse.cz> writes:
> Hi Jeff,
>
> On Tue 09-10-18 15:43:41, Jeff Moyer wrote:
>> I'm intrigued by the use case. Do I understand you correctly that the
>> database in question does not intend to make data persistent from
>> userspace? In other words, fsync/msync system calls are being issued by
>> the database?
>
> Yes, at least at the initial stage, they use fsync / msync to persist data.
OK.
>> I guess what I'm really after is a statement of requirements or
>> expectations. It would be great if you could convince the database
>> developer to engage in this discussion directly.
>
> So I talked to them and what they really look after is the control over the
> amount of memory needed by the kernel. And they are right that if your
> storage needs page cache, the amount of memory you need to set aside for the
> kernel is larger.
OK, thanks a lot for following up, Jan!
-Jeff
prev parent reply other threads:[~2018-10-16 12:35 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 10:05 Problems with VM_MIXEDMAP removal from /proc/<pid>/smaps Jan Kara
2018-10-02 10:50 ` Michal Hocko
2018-10-02 13:32 ` Jan Kara
2018-10-02 12:10 ` Johannes Thumshirn
2018-10-02 14:20 ` Johannes Thumshirn
2018-10-02 14:45 ` Christoph Hellwig
2018-10-02 15:01 ` Johannes Thumshirn
2018-10-02 15:06 ` Christoph Hellwig
2018-10-04 10:09 ` Johannes Thumshirn
2018-10-05 6:25 ` Christoph Hellwig
2018-10-05 6:35 ` Johannes Thumshirn
2018-10-06 1:17 ` Dan Williams
2018-10-14 15:47 ` Dan Williams
2018-10-17 20:01 ` Dan Williams
2018-10-18 17:43 ` Jan Kara
2018-10-18 19:10 ` Dan Williams
2018-10-19 3:01 ` Dave Chinner
2018-10-02 14:29 ` Jan Kara
2018-10-02 14:37 ` Christoph Hellwig
2018-10-02 14:44 ` Johannes Thumshirn
2018-10-02 14:52 ` Christoph Hellwig
2018-10-02 15:31 ` Jan Kara
2018-10-02 20:18 ` Dan Williams
2018-10-03 12:50 ` Jan Kara
2018-10-03 14:38 ` Dan Williams
2018-10-03 15:06 ` Jan Kara
2018-10-03 15:13 ` Dan Williams
2018-10-03 16:44 ` Jan Kara
2018-10-03 21:13 ` Dan Williams
2018-10-04 10:04 ` Johannes Thumshirn
2018-10-02 15:07 ` Jan Kara
2018-10-17 20:23 ` Jeff Moyer
2018-10-18 0:25 ` Dave Chinner
2018-10-18 14:55 ` Jan Kara
2018-10-19 0:43 ` Dave Chinner
2018-10-30 6:30 ` Dan Williams
2018-10-30 22:49 ` Dave Chinner
2018-10-30 22:59 ` Dan Williams
2018-10-31 5:59 ` y-goto
2018-11-01 23:00 ` Dave Chinner
2018-11-02 1:43 ` y-goto
2018-10-18 21:05 ` Jeff Moyer
2018-10-09 19:43 ` Jeff Moyer
2018-10-16 8:25 ` Jan Kara
2018-10-16 12:35 ` Jeff Moyer [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=x49d0sahxxn.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@lists.01.org \
/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).