public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>, dgc@sgi.com
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] kill no-op buf macros
Date: Mon, 31 Jul 2006 09:08:15 +1000	[thread overview]
Message-ID: <20060731090815.B2280998@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <44CC2A55.6030207@sandeen.net>; from sandeen@sandeen.net on Sat, Jul 29, 2006 at 10:41:09PM -0500

On Sat, Jul 29, 2006 at 10:41:09PM -0500, Eric Sandeen wrote:
> It looks like these macros are not particularly interesting... this patch kills 
> them.

Hmm, I'm not sure about some of these..

> #define XFS_BUF_BUSY(bp)	do { } while (0)
> #define XFS_BUF_ISBUSY(bp)	(1)

This ones used on 2.4, I'd like to get Daves thoughts on whether
we do the right thing here based on his buffer cache fu.

> #define XFS_BUF_SHUT(bp)	do { } while (0)
> #define XFS_BUF_UNSHUT(bp)	do { } while (0)
> #define XFS_BUF_ISSHUT(bp)	(0)

Ditto (not used on 2.4 though, but still maybe we should be doing
something here).

> #define XFS_BUF_ISUNINITIAL(bp)	(0)

This can go, unwritten extents don't use this interface on Linux.

> #define XFS_BUF_BP_ISMAPPED(bp)	(1)

*nod* - looks like it should go.

(could you regen the patch with just these two for now?  they are
pretty much self-contained changes, and nice 'n small)

> #define XFS_BUF_SET_START(bp)			do { } while (0)

Not sure what this used to do - Dave?

> #define XFS_BUF_SET_VTYPE_REF(bp, type, ref)	do { } while (0)
> #define XFS_BUF_SET_VTYPE(bp, type)		do { } while (0)
> #define XFS_BUF_SET_REF(bp, ref)		do { } while (0)

These ones should probably be implemented properly, not removed.
We currently treat all metadata buffers with an equal ranking when
we're delwri flushing them to try to reclaim memory, this was a
scheme to indicate some are more precious than others... we have
a (currently ignored) priority passed into xfsbufd_wakeup that we
could start honouring and improve our low memory handling there..
d'ya want to hack something up there?

cheers.

- 
Nathan

  reply	other threads:[~2006-07-30 23:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-30  3:41 [PATCH] kill no-op buf macros Eric Sandeen
2006-07-30 23:08 ` Nathan Scott [this message]
2006-07-31  0:25   ` Eric Sandeen
2006-07-31  4:03   ` Eric Sandeen
2006-08-09  1:24   ` David Chinner
2006-08-09  2:43     ` Eric Sandeen

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=20060731090815.B2280998@wobbly.melbourne.sgi.com \
    --to=nathans@sgi.com \
    --cc=dgc@sgi.com \
    --cc=sandeen@sandeen.net \
    --cc=xfs@oss.sgi.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