public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Trevor Woollacott [ MTN - Innovation Centre ]" <Woolla_T@mtn.co.za>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: POSIX_FADV_DONTNEED
Date: Thu, 14 Aug 2008 09:15:21 -0700	[thread overview]
Message-ID: <20080814091521.e4d9be53.akpm@linux-foundation.org> (raw)
In-Reply-To: <70D00C33FCD1FD4A860DEAC228277C0C048425EA@MTNMAIL1.mtn.co.za>

On Thu, 14 Aug 2008 12:26:28 +0200 "Trevor Woollacott [ MTN - Innovation Centre ]" <Woolla_T@mtn.co.za> wrote:

> 
> > On Fri, 1 Aug 2008 17:05:39 +0200 "Trevor Woollacott [ MTN - Innovation
> > Centre ]" <Woolla_T@mtn.co.za> wrote:

(please don't top-post).

> > > 
> > > Hi all
> > > 
> > > Does anyone know if posix_fadvise() with POSIX_FADV_DONTNEED is
> > > blocking/unblocking?
> > 
> > It tries to be nonblocking and will mostly succeed in that.  It might
> > occasionally block on a metadata read or journal congestion or
> > something, so it isn't guaranteed.
> >
>
> Thanks for the response Andrew. Is there a way to check when the cached
> data has been freed after fadvise has been called?
> 

I assume you meant "whether", not "when".

Not directly.  I believe that the best way of obtaining that
information remains mmap()ing the file then querying the presence of
pages via mincore().

  reply	other threads:[~2008-08-14 16:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01 15:05 POSIX_FADV_DONTNEED Trevor Woollacott [ MTN - Innovation Centre ]
2008-08-14  9:17 ` POSIX_FADV_DONTNEED Andrew Morton
2008-08-14 10:26   ` POSIX_FADV_DONTNEED Trevor Woollacott [ MTN - Innovation Centre ]
2008-08-14 16:15     ` Andrew Morton [this message]
2008-08-15  8:23       ` POSIX_FADV_DONTNEED Trevor Woollacott [ MTN - Innovation Centre ]

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=20080814091521.e4d9be53.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=Woolla_T@mtn.co.za \
    --cc=linux-kernel@vger.kernel.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