public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
To: jaxboe@fusionio.com, vgoyal@redhat.com, jmarchan@redhat.com,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: [RFC][PATCH 0/2 v6] blk: fix a wrong accounting of hd_struct->in_flight
Date: Mon, 06 Dec 2010 18:44:24 +0900	[thread overview]
Message-ID: <4CFCB078.3030905@jp.fujitsu.com> (raw)

Hi Jens, Linus, Vivek, Jerome,

Do you remember following problem?

https://lkml.org/lkml/2010/10/24/118

I try to fix a original problem, which is a wrong accounting of
hd_struct->in_flight, by completely rewriting a patch.

Here are patches for fixing the original problem.

  [PATCH 1/2] Don't merge different partition's IOs
  [PATCH 1/2] Change a argument of disk_map_sector_rcu() to
              hd_part->start_sect from req->__sector

For more details, please refer to the header of each patch.

Any comments or questions are welcome.

Thanks.
Yasuaki Ishimatsu


                 reply	other threads:[~2010-12-06  9:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4CFCB078.3030905@jp.fujitsu.com \
    --to=isimatu.yasuaki@jp.fujitsu.com \
    --cc=jaxboe@fusionio.com \
    --cc=jmarchan@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vgoyal@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