linux-kernel - Re: [take12 0/3] kevent: Generic event handling mechanism.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1156321130.2476.275.camel@entropy>
Date:	Wed, 23 Aug 2006 01:18:50 -0700
From:	Nicholas Miell <nmiell@...cast.net>
To:	David Miller <davem@...emloft.net>
Cc:	akpm@...l.org, johnpol@....mipt.ru, sundell.software@...il.com,
	kuznet@....inr.ac.ru, linux-kernel@...r.kernel.org,
	drepper@...hat.com, netdev@...r.kernel.org, zach.brown@...cle.com,
	hch@...radead.org
Subject: Re: [take12 0/3] kevent: Generic event handling mechanism.

On Wed, 2006-08-23 at 00:35 -0700, David Miller wrote:
> From: Andrew Morton <akpm@...l.org>
> Date: Wed, 23 Aug 2006 00:07:58 -0700
> 
> > I wonder whether designing-in a millisecond granularity is the right thing
> > to do.  If in a few years the kernel is running tickless with high-res clock
> > interrupt sources, that might look a bit lumpy.
> > 
> > Switching it to a __u64 nanosecond counter would be basically free on
> > 64-bit machines, and not very expensive on 32-bit, no?
> 
> If it ends up in a structure we'll need to use the "aligned_u64" type
> in order to avoid problems with 32-bit x86 binaries running on 64-bit
> kernels.

Perhaps

struct timespec64
{
	uint64_t tv_sec __attribute__((aligned(8)));
	uint32_t tv_nsec;
}

with a snide remark about gcc in the comments?

-- 
Nicholas Miell <nmiell@...cast.net>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/