From: David Woodhouse <dwmw2@infradead.org>
To: acurtis@onz.com
Cc: "Jasmine Strong" <jasmine@hex.linuxgrrls.org>,
"John Hall" <John.Hall@optionexist.co.uk>,
"Linux MTD list (E-mail)" <linux-mtd@lists.infradead.org>
Subject: Re: Stable cvs version for 2.4
Date: Wed, 04 Sep 2002 16:54:28 +0100 [thread overview]
Message-ID: <10914.1031154868@redhat.com> (raw)
In-Reply-To: <NCBBIINEHIPFGJPLBEIFIEKODLAA.acurtis@onz.com>
acurtis@onz.com said:
> Just pick a method that will work for all. No sense in cluttering the
> code with conditional compile stuff because we can not choose an
> implementation. How about we make the flags element either a byte or a
> word depending on architecture. This would only result in a structure
> redefinition and not affect the rest of the code.
If we're going to do that, we might as well just use a byte and not even
have the #define.
In the common case, on the architectures where stuff will be aligned, the
compiler will automatically pad that out so it takes 32 bits anyway, and
there's no difference. In the case where the compiler doesn't pad, we gain
three bytes per object.
If we're not going to avoid those 32 bits in the common case, it's not
really worth the effort.
--
dwmw2
next prev parent reply other threads:[~2002-09-04 15:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 10:09 Stable cvs version for 2.4 John Hall
2002-09-03 12:29 ` David Woodhouse
2002-09-04 0:18 ` David Woodhouse
2002-09-04 1:14 ` Jasmine Strong
2002-09-04 8:51 ` David Woodhouse
2002-09-04 14:21 ` Jasmine Strong
2002-09-04 14:37 ` David Woodhouse
2002-09-04 14:46 ` Allen Curtis
2002-09-04 14:54 ` Jasmine Strong
2002-09-04 15:17 ` Steve Wahl
2002-09-04 15:26 ` David Woodhouse
2002-09-04 15:20 ` David Woodhouse
2002-09-04 15:33 ` Jasmine Strong
2002-09-04 15:44 ` David Woodhouse
2002-09-04 15:50 ` Allen Curtis
2002-09-04 15:54 ` David Woodhouse [this message]
2002-09-04 14:49 ` Jasmine Strong
2002-09-04 15:06 ` David Woodhouse
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=10914.1031154868@redhat.com \
--to=dwmw2@infradead.org \
--cc=John.Hall@optionexist.co.uk \
--cc=acurtis@onz.com \
--cc=jasmine@hex.linuxgrrls.org \
--cc=linux-mtd@lists.infradead.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