From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Christoph Hellwig <hch@infradead.org>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
michaelc@cs.wisc.edu, linux-fsdevel@vger.kernel.org,
ext2-devel@lists.sourceforge.net, open-iscsi@googlegroups.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: allowed pages in the block later, was Re: [Ext2-devel] [PATCH] ext3: avoid sending down non-refcounted pages
Date: Thu, 8 Dec 2005 15:58:46 +0200 [thread overview]
Message-ID: <84144f020512080558tb9bb6bbjf91e72ad3d9ccaa6@mail.gmail.com> (raw)
In-Reply-To: <20051208134239.GA13376@infradead.org>
Hi Christoph,
On 12/8/05, Christoph Hellwig <hch@infradead.org> wrote:
> One way to work around that would be to detect kmalloced pages and use
> a slowpath for that. The major issues with that is that we don't have a
> reliable way to detect if a given struct page comes from the slab allocator
> or not.
Why doesn't PageSlab work for you?
Pekka
next prev parent reply other threads:[~2005-12-08 13:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 9:09 [PATCH] ext3: avoid sending down non-refcounted pages FUJITA Tomonori
2005-12-08 10:18 ` Andreas Dilger
2005-12-08 12:39 ` [Ext2-devel] " FUJITA Tomonori
2005-12-08 13:42 ` allowed pages in the block later, was " Christoph Hellwig
2005-12-08 13:58 ` Pekka Enberg [this message]
2005-12-12 17:27 ` allowed pages in the block later, was " Christoph Hellwig
2005-12-08 18:18 ` allowed pages in the block later, was Re: [Ext2-devel] " Mike Christie
2005-12-08 18:22 ` Mike Christie
2005-12-08 19:20 ` Pekka Enberg
2005-12-11 0:47 ` Andrew Morton
2005-12-11 8:44 ` allowed pages in the block later, was " Arjan van de Ven
2005-12-12 17:25 ` allowed pages in the block later, was Re: [Ext2-devel] " Christoph Hellwig
2005-12-12 20:12 ` Andrew Morton
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=84144f020512080558tb9bb6bbjf91e72ad3d9ccaa6@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=ext2-devel@lists.sourceforge.net \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=michaelc@cs.wisc.edu \
--cc=open-iscsi@googlegroups.com \
/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).