linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martin Jambor <jambormartin@gmail.com>
To: Linux FS Development List <linux-fsdevel@vger.kernel.org>
Subject: Re: pagevec_lookup_tag() and pagevec_release() substitutes and an OOM
Date: Wed, 8 Feb 2006 06:01:09 +0100	[thread overview]
Message-ID: <9615ac9b0602072101i527eac16jfb956a9437df493d@mail.gmail.com> (raw)
In-Reply-To: <9615ac9b0602071629y5054dc07w8d1f18e070b0b01f@mail.gmail.com>

Please disregard my previous post, I have found the bug right at the
spot where I've been starring for the last two days. (I knew this
would happen, I am sorry but I guess if I didn't send the mail, it
would take me even longer to discover what was going on).

The trouble was I was not removing pages from LRU and mm didn't like that.

However, why are not pagevec functions exported for modules? They seem
very useful and I hate to cut and paste stuff.

Thanks very much anyway,

Martin

On 2/8/06, Martin Jambor <jambormartin@gmail.com> wrote:
> Hi all,
>
> I am implementing aops->writepages of a filesystem and for various
> reasons I cannot use mpage_writepages. On the other hand, I would like
> to do be able to get a vector of pages and process it page by page (in
> my way) just like mpage_writepages gets pages...

  reply	other threads:[~2006-02-08  5:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-08  0:29 pagevec_lookup_tag() and pagevec_release() substitutes and an OOM Martin Jambor
2006-02-08  5:01 ` Martin Jambor [this message]
2006-02-08  7:48   ` Andrew Morton
2006-02-08 14:55     ` Dave Kleikamp

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=9615ac9b0602072101i527eac16jfb956a9437df493d@mail.gmail.com \
    --to=jambormartin@gmail.com \
    --cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).