linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Kleikamp <shaggy@austin.ibm.com>
To: gnb@sgi.com, David Chinner <dgc@sgi.com>
Cc: Bharata B Rao <bharata@in.ibm.com>,
	Dipankar Sarma <dipankar@in.ibm.com>,
	linux-mm@kvack.org
Subject: Re: [PATCH] dcache: separate slab for directory dentries
Date: Thu, 06 Oct 2005 07:28:50 -0500	[thread overview]
Message-ID: <1128601731.9358.2.camel@kleikamp.austin.ibm.com> (raw)
In-Reply-To: <20051006062739.GP9519161@melbourne.sgi.com>

On Thu, 2005-10-06 at 16:27 +1000, David Chinner wrote:
> +/*
> + * If the given dentry is not suitable for the inode, reallocate
> + * it, copy across the dentry's data and return the new one.  Only
> + * useful when the dentry has not yet been attached to inode or
> + * hashed, which is why it's a lot simpler than d_move().  Returns
> + * NULL if the dentry is suitable,  Called with dcache_lock, drops
> + * and regains.
> + */
> +static struct dentry * d_realloc_for_inode(struct dentry * dentry,
> +					   struct inode *inode)
> +{
> +	int flags = 0;
> +	struct dentry *new;
> +	struct dentry *parent;
> +	
> +	BUG_ON(dentry == NULL);
> +	BUG_ON(dentry->d_inode != NULL);
> +	BUG_ON(inode == NULL);
> +	BUG_ON(dentry->d_parent == NULL || dentry->d_parent == dentry);
> +
> +	if (S_ISDIR(inode->i_mode))
> +		flags |= DCACHE_DIRSLAB;
> +	if ((flags & DCACHE_DIRSLAB) == (dentry->d_flags & DCACHE_DIRSLAB))
> +		return NULL;	/* dentry is suitable */
> +
> +	parent = dentry->d_parent;
> +	list_del_init(&dentry->d_child);
> +
> +	spin_unlock(&dcache_lock);
> +	
> +	new = __d_alloc(parent, &dentry->d_name, dentry->d_flags | flags);
> +
> +	spin_lock(&dcache_lock);
> +
> +	BUG_ON(new == NULL);	/* TODO */
> +	if (new) {
> +//		new->d_op = dentry->d_op;
> +//		new->d_fsdata = dentry->d_fsdata;
> +	}
> +	
> +	return new;
> +}

Isn't this leaking the original dentry?  Shouldn't it be doing a dput or
at least a d_free here?
-- 
David Kleikamp
IBM Linux Technology Center

--
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>

  reply	other threads:[~2005-10-06 12:27 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-11 10:57 VM balancing issues on 2.6.13: dentry cache not getting shrunk enough Theodore Ts'o
2005-09-11 12:00 ` Dipankar Sarma
2005-09-12  3:16   ` Theodore Ts'o
2005-09-12  6:16     ` Martin J. Bligh
2005-09-12 12:53       ` Bharata B Rao
2005-09-13  8:47     ` Bharata B Rao
2005-09-13 21:59       ` David Chinner
2005-09-14  9:01         ` Andi Kleen
2005-09-14  9:16           ` Manfred Spraul
2005-09-14  9:43             ` Andrew Morton
2005-09-14  9:52               ` Dipankar Sarma
2005-09-14 22:44               ` Theodore Ts'o
2005-09-14  9:35           ` Andrew Morton
2005-09-14 13:57           ` Martin J. Bligh
2005-09-14 15:37             ` Sonny Rao
2005-09-15  7:21             ` Helge Hafting
2005-09-14 22:48           ` David Chinner
2005-09-14 15:48         ` Sonny Rao
2005-09-14 22:02           ` David Chinner
2005-09-14 22:40             ` Sonny Rao
2005-09-15  1:14               ` David Chinner
2005-10-06  6:27         ` [PATCH] dcache: separate slab for directory dentries David Chinner, gnb
2005-10-06 12:28           ` Dave Kleikamp [this message]
2005-10-07  3:54             ` Greg Banks
2005-10-07 13:00               ` Dave Kleikamp
2005-09-14 21:34       ` VM balancing issues on 2.6.13: dentry cache not getting shrunk enough Marcelo Tosatti
2005-09-14 21:43         ` Dipankar Sarma
2005-09-15  4:28         ` Bharata B Rao
2005-09-14 23:08       ` Marcelo Tosatti
2005-09-15  9:39         ` Bharata B Rao
2005-09-15 13:29           ` Marcelo Tosatti
2005-10-02 16:32             ` Bharata B Rao
2005-10-02 20:06               ` Marcelo
2005-10-04 13:36                 ` shrinkable cache statistics [was Re: VM balancing issues on 2.6.13: dentry cache not getting shrunk enough] Bharata B Rao
2005-10-05 21:25                   ` Marcelo Tosatti
2005-10-07  8:12                     ` Bharata B Rao

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=1128601731.9358.2.camel@kleikamp.austin.ibm.com \
    --to=shaggy@austin.ibm.com \
    --cc=bharata@in.ibm.com \
    --cc=dgc@sgi.com \
    --cc=dipankar@in.ibm.com \
    --cc=gnb@sgi.com \
    --cc=linux-mm@kvack.org \
    /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