All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cédric Villemain" <cedric@2ndquadrant.com>
To: linux-mm@kvack.org
Cc: Johannes Weiner <hannes@cmpxchg.org>
Subject: mincore() & fincore()
Date: Thu, 25 Jul 2013 16:58:33 +0200	[thread overview]
Message-ID: <201307251658.33548.cedric@2ndquadrant.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]

Hello

First, the proposed changes in this email are to be used at least for 
PostgreSQL extensions, maybe for core.

Purpose is to offer better monitoring/tracking of the hot/cold areas (and 
read/write paterns) in the tables and indexes, in PostgreSQL those are by default 
written in segments of 1GB.

There are some possible usecase already:

 * planning of hardware upgrade
 * easier configuration setup (both PostgreSQL and linux)
 * provide more informations to the planner/executor of PostgreSQL

My ideas so far are to 

 * improve mincore() in linux and add it information like in freeBSD (at 
   least adding 'mincore_modified' to track clean vs dirty pages).
 * adding fincore() to make the information easier to grab from PostgreSQL (no 
   mmap)
 * maybe some access to those stats in /proc/

It makes years that libprefetch, mincore() and fincore() are discussed on linux 
mailling lists. And they got a good feedback... So I hope it is ok to keep on 
those and provide updated patches.

Johannes, I add you in CC because you're the last one who proposed something. Should I update your patch ?

-- 
Cédric Villemain +33 (0)6 20 30 22 52
http://2ndQuadrant.fr/
PostgreSQL: Support 24x7 - Développement, Expertise et Formation

[-- Attachment #2: Type: text/html, Size: 6541 bytes --]

             reply	other threads:[~2013-07-25 14:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25 14:58 Cédric Villemain [this message]
2013-07-25 15:07 ` mincore() & fincore() Cédric Villemain
2013-07-25 15:32   ` Johannes Weiner
2013-07-26  1:55     ` Wanpeng Li
2013-07-27 20:08       ` Cédric Villemain
2013-07-26  1:55     ` Wanpeng Li

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=201307251658.33548.cedric@2ndquadrant.com \
    --to=cedric@2ndquadrant.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.