public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: cmm@us.ibm.com, sandeen@redhat.com, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: Free ext4_prealloc_space using kmem_cache_free
Date: Mon, 13 Oct 2008 12:41:32 -0400	[thread overview]
Message-ID: <20081013164132.GC17792@mit.edu> (raw)
In-Reply-To: <1223914443-25000-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>

On Mon, Oct 13, 2008 at 09:44:03PM +0530, Aneesh Kumar K.V wrote:
> We should use kmem_cache_free to free memory allocated
> via kmem_cache_alloc

Thanks, queued.

						- Ted

  reply	other threads:[~2008-10-13 16:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-13 16:14 [PATCH] ext4: Free ext4_prealloc_space using kmem_cache_free Aneesh Kumar K.V
2008-10-13 16:41 ` Theodore Tso [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-10-14  6:33 Patches for patchqueue Aneesh Kumar K.V
2008-10-14  6:33 ` [PATCH -V5] ext4: Use an rbtree for tracking blocks freed during transaction Aneesh Kumar K.V
2008-10-14  6:33   ` [PATCH] ext4: Use tag dirty lookup during mpage_da_submit_io Aneesh Kumar K.V
2008-10-14  6:33     ` [PATCH] vfs: Remove the range_cont writeback mode Aneesh Kumar K.V
2008-10-14  6:33       ` [PATCH] vfs: Add no_nrwrite_update and no_index_update writeback control flags Aneesh Kumar K.V
2008-10-14  6:33         ` [PATCH] ext4: Fix file fragmentation during large file write Aneesh Kumar K.V
2008-10-14  6:33           ` [PATCH] ext4: Free ext4_prealloc_space using kmem_cache_free Aneesh Kumar K.V

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=20081013164132.GC17792@mit.edu \
    --to=tytso@mit.edu \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=cmm@us.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.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