From: Al Viro <viro@ZenIV.linux.org.uk>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: chris.mason@oracle.com, akpm@linux-foundation.org,
adilger@sun.com, tytso@mit.edu, mfasheh@suse.com,
joel.becker@oracle.com, matthew@wil.cx,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
ocfs2-devel@oss.oracle.com, linux-mm@kvack.org,
ngupta@vflare.org, jeremy@goop.org, JBeulich@novell.com,
kurt.hackel@oracle.com, npiggin@suse.de,
dave.mccracken@oracle.com, riel@redhat.com
Subject: Re: Cleancache [PATCH 2/7] (was Transcendent Memory): core files
Date: Sat, 15 May 2010 00:18:15 +0100 [thread overview]
Message-ID: <20100514231815.GY30031@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20100422132809.GA27302@ca-server1.us.oracle.com>
On Thu, Apr 22, 2010 at 06:28:09AM -0700, Dan Magenheimer wrote:
> +struct cleancache_ops {
> + int (*init_fs)(unsigned long);
unsigned long? Really? Not even size_t?
> + int (*init_shared_fs)(char *uuid, unsigned long);
Ditto.
> + int (*get_page)(int, unsigned long, unsigned long, struct page *);
Ugh. First of all, presumably you have some structure behind that index,
don't you? Might be a better way to do it.
What's more, use of ->i_ino is simply wrong. How stable do you want that
to be and how much do you want it to outlive struct address_space in question?
>From my reading of your code, it doesn't outlive that anyway, so...
The third one is pgoff_t; again, use sane types, _if_ you actually want
the argument #3 at all - it can be derived from struct page you are passing
there as well.
> + int (*put_page)(int, unsigned long, unsigned long, struct page *);
> + int (*flush_page)(int, unsigned long, unsigned long);
> + int (*flush_inode)(int, unsigned long);
> + void (*flush_fs)(int);
Same questions as above...
WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: chris.mason@oracle.com, akpm@linux-foundation.org,
adilger@sun.com, tytso@mit.edu, mfasheh@suse.com,
joel.becker@oracle.com, matthew@wil.cx,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
ocfs2-devel@oss.oracle.com, linux-mm@kvack.org,
ngupta@vflare.org, jeremy@goop.org, JBeulich@novell.com,
kurt.hackel@oracle.com, npiggin@suse.de,
dave.mccracken@oracle.com, riel@redhat.com
Subject: [Ocfs2-devel] Cleancache [PATCH 2/7] (was Transcendent Memory): core files
Date: Fri, 14 May 2010 23:18:29 -0000 [thread overview]
Message-ID: <20100514231815.GY30031@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20100422132809.GA27302@ca-server1.us.oracle.com>
On Thu, Apr 22, 2010 at 06:28:09AM -0700, Dan Magenheimer wrote:
> +struct cleancache_ops {
> + int (*init_fs)(unsigned long);
unsigned long? Really? Not even size_t?
> + int (*init_shared_fs)(char *uuid, unsigned long);
Ditto.
> + int (*get_page)(int, unsigned long, unsigned long, struct page *);
Ugh. First of all, presumably you have some structure behind that index,
don't you? Might be a better way to do it.
What's more, use of ->i_ino is simply wrong. How stable do you want that
to be and how much do you want it to outlive struct address_space in question?
From my reading of your code, it doesn't outlive that anyway, so...
The third one is pgoff_t; again, use sane types, _if_ you actually want
the argument #3 at all - it can be derived from struct page you are passing
there as well.
> + int (*put_page)(int, unsigned long, unsigned long, struct page *);
> + int (*flush_page)(int, unsigned long, unsigned long);
> + int (*flush_inode)(int, unsigned long);
> + void (*flush_fs)(int);
Same questions as above...
WARNING: multiple messages have this Message-ID (diff)
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: chris.mason@oracle.com, akpm@linux-foundation.org,
adilger@sun.com, tytso@mit.edu, mfasheh@suse.com,
joel.becker@oracle.com, matthew@wil.cx,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
ocfs2-devel@oss.oracle.com, linux-mm@kvack.org,
ngupta@vflare.org, jeremy@goop.org, JBeulich@novell.com,
kurt.hackel@oracle.com, npiggin@suse.de,
dave.mccracken@oracle.com, riel@redhat.com
Subject: Re: Cleancache [PATCH 2/7] (was Transcendent Memory): core files
Date: Sat, 15 May 2010 00:18:15 +0100 [thread overview]
Message-ID: <20100514231815.GY30031@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20100422132809.GA27302@ca-server1.us.oracle.com>
On Thu, Apr 22, 2010 at 06:28:09AM -0700, Dan Magenheimer wrote:
> +struct cleancache_ops {
> + int (*init_fs)(unsigned long);
unsigned long? Really? Not even size_t?
> + int (*init_shared_fs)(char *uuid, unsigned long);
Ditto.
> + int (*get_page)(int, unsigned long, unsigned long, struct page *);
Ugh. First of all, presumably you have some structure behind that index,
don't you? Might be a better way to do it.
What's more, use of ->i_ino is simply wrong. How stable do you want that
to be and how much do you want it to outlive struct address_space in question?
>From my reading of your code, it doesn't outlive that anyway, so...
The third one is pgoff_t; again, use sane types, _if_ you actually want
the argument #3 at all - it can be derived from struct page you are passing
there as well.
> + int (*put_page)(int, unsigned long, unsigned long, struct page *);
> + int (*flush_page)(int, unsigned long, unsigned long);
> + int (*flush_inode)(int, unsigned long);
> + void (*flush_fs)(int);
Same questions as above...
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-05-14 23:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 13:28 Cleancache [PATCH 2/7] (was Transcendent Memory): core files Dan Magenheimer
2010-04-22 13:28 ` Dan Magenheimer
2010-05-14 23:18 ` Al Viro [this message]
2010-05-14 23:18 ` [Ocfs2-devel] " Al Viro
2010-05-14 23:18 ` Al Viro
2010-05-24 20:02 ` Dan Magenheimer
2010-05-24 20:04 ` [Ocfs2-devel] " Dan Magenheimer
2010-05-24 20:02 ` Dan Magenheimer
2010-05-24 20:02 ` Dan Magenheimer
2010-05-25 2:15 ` Dan Magenheimer
2010-05-25 2:16 ` [Ocfs2-devel] " Dan Magenheimer
2010-05-25 2:15 ` Dan Magenheimer
2010-05-25 2:15 ` Dan Magenheimer
-- strict thread matches above, loose matches on Subject: below --
2010-04-22 13:28 Dan Magenheimer
2010-04-22 13:28 Dan Magenheimer
2010-04-22 13:28 Dan Magenheimer
2010-04-22 12:14 Dan Magenheimer
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=20100514231815.GY30031@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=JBeulich@novell.com \
--cc=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=dave.mccracken@oracle.com \
--cc=jeremy@goop.org \
--cc=joel.becker@oracle.com \
--cc=kurt.hackel@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew@wil.cx \
--cc=mfasheh@suse.com \
--cc=ngupta@vflare.org \
--cc=npiggin@suse.de \
--cc=ocfs2-devel@oss.oracle.com \
--cc=riel@redhat.com \
--cc=tytso@mit.edu \
/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.