From: "Stephen C. Biggs" <s.biggs@softier.com>
To: "David S. Miller" <davem@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Bug in kernel code?
Date: Tue, 27 Aug 2002 17:40:41 -0700 [thread overview]
Message-ID: <3D6BB999.5183.3D4AB9@localhost> (raw)
In-Reply-To: <20020827.172924.107290535.davem@redhat.com>
On 27 Aug 2002 at 17:29, David S. Miller wrote:
> From: "Stephen C. Biggs" <s.biggs@softier.com>
> Date: Tue, 27 Aug 2002 17:32:58 -0700
>
> This is a "do while" loop so the first test is always done
>
> No, a "do while" loop always executes the first iteration.
> What version of the C language do you think we are using?
>
You're misunderstanding me, I meant that the first test is done AFTER the first iteration is
executed, so my fix is correct since, even if order is 0 because at least one iteration of the loop
is done, and the post decrement makes sure that the test succeeds if order was 0 going into the
loop.
Changing order to a signed long loses half of the cache entries due to the number being divided by
2.
next prev parent reply other threads:[~2002-08-28 0:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D6BB5C3.16057.2E515C@localhost>
[not found] ` <20020827.172304.22017977.davem@redhat.com>
2002-08-28 0:32 ` Bug in kernel code? Stephen C. Biggs
2002-08-28 0:29 ` David S. Miller
2002-08-28 0:40 ` Stephen C. Biggs [this message]
2002-08-28 0:42 ` David S. Miller
2002-08-28 1:09 ` Stephen C. Biggs
2002-08-28 1:09 ` David S. Miller
2002-08-28 1:24 ` Stephen C. Biggs
2002-08-28 1:23 ` David S. Miller
2002-08-28 2:42 ` Stephen C. Biggs
2002-08-28 3:39 ` David S. Miller
2002-08-28 3:57 ` Luca Barbieri
2002-08-28 3:58 ` David S. Miller
2002-08-28 4:10 ` Luca Barbieri
2002-08-28 4:07 ` David S. Miller
2002-08-28 4:29 ` Luca Barbieri
2002-08-28 4:29 ` Stephen Biggs
2002-08-28 4:26 ` David S. Miller
2002-08-28 21:54 ` H. Peter Anvin
2002-08-28 2:49 ` Re[2]: " Stephen C. Biggs
2002-08-28 0:54 ` Stephen C. Biggs
2002-08-28 0:25 Stephen C. Biggs
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=3D6BB999.5183.3D4AB9@localhost \
--to=s.biggs@softier.com \
--cc=davem@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.