From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Tasklet usage?
Date: Sat, 16 Oct 2004 11:53:35 -0600 [thread overview]
Message-ID: <003201c4b3a9$0f0a6180$6601a8c0@northbrook> (raw)
In-Reply-To: fa.doac9ep.1ckig8r@ifi.uio.no
If you want an exact size, int32_t, uint32_t, etc. are what you'd need to
use.. Typically "long" is the biggest that can be handled in single machine
instructions, though there is no guarantee of this (I think the language
standard only guarantees that long is as least as big as int and at least 32
bits).
----- Original Message -----
From: "Pierre Ossman" <drzeus-list@drzeus.cx>
Newsgroups: fa.linux.kernel
To: "Roland Dreier" <roland@topspin.com>
Cc: "LKML" <linux-kernel@vger.kernel.org>
Sent: Saturday, October 16, 2004 10:37 AM
Subject: Re: Tasklet usage?
> Roland Dreier wrote:
>
>>unsigned long will be 64 bits on a 64-bit system. There are many
>>places in the Linux kernel where we assume that void * and long are
>>the same size.
>>
>> - Roland
>>
> Just out of curiosity, how do you declare a 32-bit int then? I thought
> longlong would be the 64-bit int under gcc and long stay as it is.
>
> Rgds
> Pierre
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2004-10-16 17:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.hf0cjfr.n3qt2d@ifi.uio.no>
[not found] ` <fa.doac9ep.1ckig8r@ifi.uio.no>
2004-10-16 17:53 ` Robert Hancock [this message]
[not found] <fa.dvqma04.n40gos@ifi.uio.no>
2004-10-16 1:46 ` Tasklet usage? Robert Hancock
2004-10-15 13:14 Pierre Ossman
2004-10-15 13:32 ` Neil Horman
2004-10-15 13:46 ` Pierre Ossman
2004-10-15 14:09 ` Neil Horman
2004-10-16 15:17 ` Pierre Ossman
2004-10-16 16:03 ` Roland Dreier
2004-10-16 16:36 ` Pierre Ossman
2004-10-16 17:51 ` Roland Dreier
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='003201c4b3a9$0f0a6180$6601a8c0@northbrook' \
--to=hancockr@shaw.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 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.