From: Tejun Heo <tj@kernel.org>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Jens Axboe <jens.axboe@oracle.com>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
Jeff Garzik <jeff@garzik.org>
Subject: Re: [PATCH #tj-block-for-linus] block: fix failfast merge testing in elv_rq_merge_ok()
Date: Thu, 16 Jul 2009 17:06:40 +0900 [thread overview]
Message-ID: <4A5EDF90.7090900@kernel.org> (raw)
In-Reply-To: <4A5EDD81.6060409@panasas.com>
Boaz Harrosh wrote:
> On 07/16/2009 09:44 AM, Tejun Heo wrote:
>> Commit ab0fd1debe730ec9998678a0c53caefbd121ed10 tries to prevent merge
>> of requests with different failfast settings. In elv_rq_merge_ok(),
>> it compares new bio's failfast flags against the merge target
>> request's. However, the flag testing accessors for bio and blk don't
>> return boolean but the tested bit value directly and FAILFAST on bio
>> and blk don't match, so directly comparing them with == results in
>> false negative unnecessary preventing merge of readahead requests.
>>
>> This patch convert the results to boolean by negating them before
>> comparison.
>
> I don't like that at all. Please fix the accessors to return
> boolean. They look and regarded as boolean. I've never seen
> them used as their bit value.
Yeah, I'll be happier that way but please note that this patch is only
for 2.6.31. 2.6.32 won't have this code at all and we're past the
merge window, so the smallest fix wins in this case, I think. Also,
changing only some of the accessors will increase the level of
confusion while changing all of them for 2.6.31 at this point is way
too invasive (there can be cases where the bit mask return value is
depended upon).
Looks like the flags are gonna go through considerable cleanup pretty
soon, so let's postpone small things till then.
> if you are concerned with performance don't
> an if(flag & bit) is even slightly slower then
> if(0 != (flag & bit)) on some processors
I wasn't worried about the performance at all.
Thanks.
--
tejun
next prev parent reply other threads:[~2009-07-16 8:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 6:44 [PATCH #tj-block-for-linus] block: fix failfast merge testing in elv_rq_merge_ok() Tejun Heo
2009-07-16 7:57 ` Boaz Harrosh
2009-07-16 8:06 ` Tejun Heo [this message]
2009-07-16 8:20 ` Boaz Harrosh
2009-07-16 8:35 ` Tejun Heo
2009-07-16 8:48 ` Boaz Harrosh
2009-07-17 5:51 ` Tejun Heo
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=4A5EDF90.7090900@kernel.org \
--to=tj@kernel.org \
--cc=bharrosh@panasas.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jeff@garzik.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.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