On Tue, Jul 10, 2007 at 12:01:51PM -0400, Lennart Sorensen wrote:
> On Sun, Jul 01, 2007 at 09:24:41PM +0200, Rodolfo Giometti wrote:
> > struct pps_timedata_s {
> > __32 sec;
> > __32 nsec;
> > }
> >
> > Ok? I think 32 bits are enought for keeping seconds... :)
>
> You want to purposely define an API that will break in 23 years (or is
> that 83 years since you made it unsigned potentially)? Why not 64bit
> for seconds and 32bit for nsec. That should cover it for long enough.
> When the unix time format was created 37 years ago, I could see thinking
> 32bit seemed reasonable, but why do it now. We have ram enough for
> 64bits.
Sorry I wrote wrong. I meant __u32.
I can use __u64 for seconds but doing this there could be problems for
32 bits platforms? =:-o
Rodolfo (not a 64 bits guru :)
--
GNU/Linux Solutions e-mail: [email protected]
Linux Device Driver [email protected]
Embedded Systems [email protected]
UNIX programming phone: +39 349 2432127
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
