public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Timothy Miller <miller@techsource.com>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] only use 48-bit lba when necessary
Date: Thu, 17 Apr 2003 11:05:30 -0500	[thread overview]
Message-ID: <20030417160530.GD23277@waste.org> (raw)
In-Reply-To: <3E9EC71B.5000901@techsource.com>

On Thu, Apr 17, 2003 at 11:24:11AM -0400, Timothy Miller wrote:
> 
> >>Yes, but:
> >>
> >>  if (expr1 && expr2)
> >>     var = true;
> >>  else
> >>     var = false;
> >>
> >>is usually better turned into something that avoids jumps
> >>when it's safe to evaluate both parts unconditionally:
> >>
> >>  var = (expr1 != 0) & (expr2 != 0);
> >>
> >>or (if you can stand it):
> >>
> >>  var = !!expr1 & !!expr2;
> >
> >Such ugly transformations are a job for compiler writers and may
> >occassionally be acceptable in some critical paths. The IO path, which
> >is literally dozens of function calls deep from read()/write() to
> >driver methods, does not qualify.
> 
> What's ugly about them? 

It doesn't pass the test of "would I use it if I didn't think it was
faster?"

As I pointed out, your variant is not faster with a reasonable
compiler, only less obvious. And none of this sort of optimization
will ever be measurably better in the IO path anyway. But every one of
these false optimizations is a barrier to the understanding that will
allow real cleanups to make fundamental improvements.

-- 
Matt Mackall : http://www.selenic.com : of or relating to the moon

  reply	other threads:[~2003-04-17 15:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-04 17:02 [PATCH] only use 48-bit lba when necessary Chuck Ebbert
2003-04-17 14:20 ` Matt Mackall
2003-04-17 15:24   ` Timothy Miller
2003-04-17 16:05     ` Matt Mackall [this message]
2003-04-17 18:49       ` Timothy Miller
  -- strict thread matches above, loose matches on Subject: below --
2003-04-18  9:50 Chuck Ebbert
2003-04-18  3:32 linux-kernel
2003-04-18  1:34 Chuck Ebbert
2003-04-18  4:18 ` Matt Mackall
2003-04-18 14:34 ` Timothy Miller
2003-04-04 12:29 Jens Axboe
2003-04-04 13:19 ` Juan Quintela
2003-04-04 13:22   ` Jens Axboe
2003-04-04 15:48     ` Juan Quintela
2003-04-04 15:54       ` Jens Axboe
2003-04-04 17:06         ` John Bradford
2003-04-04 14:40 ` Andries Brouwer
2003-04-04 15:13   ` 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=20030417160530.GD23277@waste.org \
    --to=mpm@selenic.com \
    --cc=76306.1226@compuserve.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miller@techsource.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