From: Vivek Goyal <vgoyal@redhat.com>
To: linux-kernel@vger.kernel.org, axboe@kernel.dk
Cc: dpshah@google.com, namhyung@gmail.com
Subject: Re: [PATCH 0/3] block: Per cpu merge stats and cfq fix
Date: Fri, 20 May 2011 20:06:50 -0400 [thread overview]
Message-ID: <20110521000650.GA8026@redhat.com> (raw)
In-Reply-To: <1305936167-8932-1-git-send-email-vgoyal@redhat.com>
On Fri, May 20, 2011 at 08:02:44PM -0400, Vivek Goyal wrote:
> Hi Jens,
>
> Here is the patch for making merge stats per cpu. While scanning the code
> I also noticed that in one case I was not freeing up per cpu stats. First
> patch fixes it. I also included Namhyung Kim's bio merge fix.
>
> Thanks
> Vivek
>
> Vivek Goyal (3):
> cfq-iosched: Fix a memory leak of per cpu stats for root group
> cfq-iosched: Make IO merge related stats per cpu
Minor correction. Following patch author is Namhyung Kim.
Namhyung Kim(1)
> block: call elv_bio_merged() when merged
Thanks
Vivek
>
> block/blk-cgroup.c | 22 +++++++++++++++++-----
> block/blk-cgroup.h | 4 ++--
> block/blk-core.c | 2 ++
> block/cfq-iosched.c | 5 +++++
> 4 files changed, 26 insertions(+), 7 deletions(-)
>
> --
> 1.7.4.4
next prev parent reply other threads:[~2011-05-21 0:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-21 0:02 [PATCH 0/3] block: Per cpu merge stats and cfq fix Vivek Goyal
2011-05-21 0:02 ` [PATCH 1/3] cfq-iosched: Fix a memory leak of per cpu stats for root group Vivek Goyal
2011-05-21 0:02 ` [PATCH 2/3] cfq-iosched: Make IO merge related stats per cpu Vivek Goyal
2011-05-21 0:02 ` [PATCH 3/3] block: call elv_bio_merged() when merged Vivek Goyal
2011-05-21 0:06 ` Vivek Goyal [this message]
2011-05-23 8:04 ` [PATCH 0/3] block: Per cpu merge stats and cfq fix Jens Axboe
2011-05-23 13:53 ` Namhyung Kim
2011-05-23 11:07 ` Namhyung Kim
2011-05-23 8:03 ` Jens Axboe
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=20110521000650.GA8026@redhat.com \
--to=vgoyal@redhat.com \
--cc=axboe@kernel.dk \
--cc=dpshah@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@gmail.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