All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [RESEND][PATCH 5/6] Provide a filesystem-specific sync'able page bit
Date: Fri, 15 Oct 2004 16:14:46 +0100	[thread overview]
Message-ID: <28682.1097853286@redhat.com> (raw)
In-Reply-To: <20041014194421.GU16153@parcelfarce.linux.theplanet.co.uk>


> > +#define PG_fs_misc		 9	/* Filesystem specific bit */
> ...
> That's not really enough documentation.  Who sets this flag?  Who clears this
> flag?

That's up to the owning filesystem (or device file, I suppose); hence
"filesystem-specific". I could expand this a little, but there isn't much to
say - it's entirely up to the filesystem, though I think I should probably
require it to be cleared before the page is freed.

> Currently, mm/page_alloc.c clears this flag:

Not really; that's irrelevant. It checks to see if it is set when it allocates
a page, and if it is it complains bitterly. It then splats this bit and all
others to make sure struct page has all its flags in the ground state.

> If you're going to not kill this flag, at least rename it so we don't
> have two defines for the same bit.

I did have it as a different number, but I was told to make it the same as
PG_checked. I could rename all instances of PG_checked, I suppose...

> which really ought to at least mention Documentation/cachetlb.txt

Fix it then.

David

WARNING: multiple messages have this Message-ID (diff)
From: David Howells <dhowells@redhat.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [RESEND][PATCH 5/6] Provide a filesystem-specific sync'able page bit
Date: Fri, 15 Oct 2004 16:14:46 +0100	[thread overview]
Message-ID: <28682.1097853286@redhat.com> (raw)
In-Reply-To: <20041014194421.GU16153@parcelfarce.linux.theplanet.co.uk>

> > +#define PG_fs_misc		 9	/* Filesystem specific bit */
> ...
> That's not really enough documentation.  Who sets this flag?  Who clears this
> flag?

That's up to the owning filesystem (or device file, I suppose); hence
"filesystem-specific". I could expand this a little, but there isn't much to
say - it's entirely up to the filesystem, though I think I should probably
require it to be cleared before the page is freed.

> Currently, mm/page_alloc.c clears this flag:

Not really; that's irrelevant. It checks to see if it is set when it allocates
a page, and if it is it complains bitterly. It then splats this bit and all
others to make sure struct page has all its flags in the ground state.

> If you're going to not kill this flag, at least rename it so we don't
> have two defines for the same bit.

I did have it as a different number, but I was told to make it the same as
PG_checked. I could rename all instances of PG_checked, I suppose...

> which really ought to at least mention Documentation/cachetlb.txt

Fix it then.

David
--
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:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2004-10-15 15:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-14 19:05 [RESEND][PATCH 5/6] Provide a filesystem-specific sync'able page bit David Howells
2004-10-14 19:05 ` David Howells
2004-10-14 19:44 ` Matthew Wilcox
2004-10-14 19:44   ` Matthew Wilcox
2004-10-15 15:14   ` David Howells [this message]
2004-10-15 15:14     ` David Howells
2004-10-15  7:29 ` Martin Waitz

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=28682.1097853286@redhat.com \
    --to=dhowells@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=matthew@wil.cx \
    /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.