Message 225906 - Python tracker

Message225906

Author	vstinner
Recipients	belopolsky, loewis, tim.peters, vstinner
Date	2014-08-25.23:40:16
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1409010016.62.0.379710490774.issue22117@psf.upfronthosting.co.za>
In-reply-to

Content
> The Linux kernel is going to use 64-bit integer even on 32-bit CPU to store timestamps, to simplify the code (to avoid the structure). Read this article: http://lwn.net/Articles/607741/ "One of the first changes merged for 3.17 is to simply get rid of the non-scalar form of ktime_t and force all architectures to use the 64-bit nanosecond count representation. This change may slow things down on 32-bit systems; in particular, conversions from other time formats may be significantly slower. But, as noted in the changelog, the ARM and x86 architectures were already using the scalar format anyway, so they will not get any slower."

Content

> The Linux kernel is going to use 64-bit integer even on 32-bit CPU to store timestamps, to simplify the code (to avoid the structure).

Read this article: http://lwn.net/Articles/607741/

"One of the first changes merged for 3.17 is to simply get rid of the non-scalar form of ktime_t and force all architectures to use the 64-bit nanosecond count representation. This change may slow things down on 32-bit systems; in particular, conversions from other time formats may be significantly slower. But, as noted in the changelog, the ARM and x86 architectures were already using the scalar format anyway, so they will not get any slower."

History
Date	User	Action	Args
2014-08-25 23:40:16	vstinner	set	recipients: + vstinner, tim.peters, loewis, belopolsky
2014-08-25 23:40:16	vstinner	set	messageid: <1409010016.62.0.379710490774.issue22117@psf.upfronthosting.co.za>
2014-08-25 23:40:16	vstinner	link	issue22117 messages
2014-08-25 23:40:16	vstinner	create