From: Hollis Blanchard <hollis@penguinppc.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
ppc64-dev <linuxppc64-dev@ozlabs.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PPC64 iSeries: cleanup viopath
Date: Tue, 15 Mar 2005 08:32:27 -0600 [thread overview]
Message-ID: <0961a209ce72bb9f2a01b163aa6e6fbd@penguinppc.org> (raw)
In-Reply-To: <20050315143412.0c60690a.sfr@canb.auug.org.au>
On Mar 14, 2005, at 9:34 PM, Stephen Rothwell wrote:
>
> Since you brought this file to my attention, I figured I might as well
> do
> some simple cleanups. This patch does:
> - single bit int bitfields are a bit suspect and Anndrew pointed
> out recently that they are probably slower to access than ints
> --- linus/arch/ppc64/kernel/viopath.c 2005-03-13 04:07:42.000000000
> +1100
> +++ linus-cleanup.1/arch/ppc64/kernel/viopath.c 2005-03-15
> 14:02:48.000000000 +1100
> @@ -56,8 +57,8 @@
> * But this allows for other support in the future.
> */
> static struct viopathStatus {
> - int isOpen:1; /* Did we open the path? */
> - int isActive:1; /* Do we have a mon msg outstanding */
> + int isOpen; /* Did we open the path? */
> + int isActive; /* Do we have a mon msg outstanding */
> int users[VIO_MAX_SUBTYPES];
> HvLpInstanceId mSourceInst;
> HvLpInstanceId mTargetInst;
Why not use a byte instead of a full int (reordering the members for
alignment)?
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2005-03-15 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 3:34 Stephen Rothwell
2005-03-15 14:32 ` Hollis Blanchard [this message]
2005-03-15 15:53 ` Stephen Rothwell
2005-03-15 17:43 ` Linas Vepstas
2005-03-15 17:49 ` Brad Boyer
2005-03-16 15:12 ` Hollis Blanchard
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=0961a209ce72bb9f2a01b163aa6e6fbd@penguinppc.org \
--to=hollis@penguinppc.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@osdl.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
Powered by JetHome