From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Bill Pringlemeir <bpringle@sympatico.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Newbie idiotic questions.
Date: Sat, 16 Jun 2001 21:32:50 -0400 [thread overview]
Message-ID: <3B2C08C2.6CC5D144@mandrakesoft.com> (raw)
In-Reply-To: <m2d78352do.fsf@sympatico.ca>
Bill Pringlemeir wrote:
> [main.c, line 175]
>
> for (count = 0; count < sizeof(card->digmix) / sizeof(card->digmix[0]); count++) {
>
> Isn't there some sort of `ALEN' macro available, or is this
> considered to muddy things by using a macro?
Yes, we have array size
> [main.c, line 223]
> if ((card->mpuout = kmalloc(sizeof(struct emu10k1_mpuout), GFP_KERNEL))
>
> Why is the struct type referenced for the allocation size? Why not,
>
> if ((card->mpuout = kmalloc(sizeof(card->mpuout), GFP_KERNEL))
because then you would be allocating the size of a pointer, not the size
of a structure
> Why aren't all the gobs of constant data in this driver declared as
> constant? Do it give a performance advantage by having the data in a
> different MMU section and better cache effects or something?
Marking data const is usually a good idea.
Jeff
--
Jeff Garzik | Andre the Giant has a posse.
Building 1024 |
MandrakeSoft |
next prev parent reply other threads:[~2001-06-17 1:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-17 1:19 Newbie idiotic questions Bill Pringlemeir
2001-06-17 1:32 ` Jeff Garzik [this message]
2001-06-17 10:48 ` Daniel Phillips
2001-06-17 12:27 ` rjd
2001-06-17 15:01 ` Daniel Phillips
2001-06-17 15:08 ` Jeff Garzik
2001-06-17 15:38 ` David Flynn
2001-06-17 15:54 ` Jeff Garzik
2001-06-17 19:18 ` Geert Uytterhoeven
2001-06-17 20:08 ` Daniel Phillips
2001-06-17 20:37 ` Alexander Viro
2001-06-17 21:28 ` Daniel Phillips
2001-06-17 22:33 ` Alexander Viro
2001-06-18 9:14 ` Roman Zippel
2001-06-18 9:30 ` Alexander Viro
2001-06-17 21:17 ` Bill Pringlemeir
2001-06-17 1:35 ` Richard B. Johnson
2001-06-17 3:01 ` Arnaldo Carvalho de Melo
2001-06-17 8:06 ` rjd
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=3B2C08C2.6CC5D144@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=bpringle@sympatico.ca \
--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