All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Jan Blunck <jblunck@suse.de>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	viro@zeniv.linux.org.uk, dgc@sgi.com
Subject: Re: [patch 0/5] [RFC] vfs: per-superblock unused dentries list
Date: Mon, 29 May 2006 11:57:27 +1000	[thread overview]
Message-ID: <20060529015727.GS8069029@melbourne.sgi.com> (raw)
In-Reply-To: <20060526110655.197949000@suse.de>

On Fri, May 26, 2006 at 01:06:55PM +0200, Jan Blunck wrote:
> BTW: Dave, I just saw that you already posted some patches but I decided to
> send my patches anyway.

No problems. Your patches remove bits that I wasn't sure could be removed,
but effectively do the same thing. Removing shrink_dcache_anon(), for example.
The question is which patchset do we want to carry forward?

I'll add more comments in replies to the various patches...

Cheers,

Dave.
-- 
Dave Chinner
R&D Software Enginner
SGI Australian Software Group

       reply	other threads:[~2006-05-29  1:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060526110655.197949000@suse.de>
2006-05-29  1:57 ` David Chinner [this message]
     [not found] ` <20060526110802.852609000@suse.de>
2006-05-29  2:24   ` [patch 4/5] vfs: per superblock dentry stats David Chinner
2006-05-29  9:43     ` Jan Blunck
     [not found] ` <20060526110803.159085000@suse.de>
2006-05-29  3:08   ` [patch 5/5] vfs: per superblock dentry unused list David Chinner
2006-05-29 11:54     ` Jan Blunck
2006-05-30  0:04       ` David Chinner
2006-05-30 10:06         ` Jan Blunck
2006-05-30 23:56           ` David Chinner

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=20060529015727.GS8069029@melbourne.sgi.com \
    --to=dgc@sgi.com \
    --cc=jblunck@suse.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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.