LWN: Comments on "A sys_poll() ABI tweak" https://lwn.net/Articles/483078/ This is a special feed containing comments posted to the individual LWN article titled "A sys_poll() ABI tweak". en-us Fri, 19 Sep 2025 15:50:35 +0000 Fri, 19 Sep 2025 15:50:35 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net A sys_poll() ABI tweak https://lwn.net/Articles/485641/ https://lwn.net/Articles/485641/ sdalley <div class="FormattedComment"> The quality of posts does vary, doesn't it.<br> <p> After reading landley's GP, and the references he supplied, I understand the subtleties of the actual situation.<br> <p> After reading khim's post, I am left completely uninformed, and with the strong impression that the poster is an arrogant twerp. It's only an impression, though, and I could be wrong ...<br> </div> Wed, 07 Mar 2012 10:39:33 +0000 A sys_poll() ABI tweak https://lwn.net/Articles/485376/ https://lwn.net/Articles/485376/ khim <blockquote><font class="QuotedText">No, int and long _aren't_ the same size on "most" architectures.</font></blockquote> <p>Of course they are!</p> <blockquote><font class="QuotedText">They're the same size on 32 bit architectures, different on 64 bit.</font></blockquote> <p>Not always and anyway: number of 32 bit architectures dwarfs the number of 64 bit architectures, so what's your point?</p> Tue, 06 Mar 2012 07:03:36 +0000 A sys_poll() ABI tweak https://lwn.net/Articles/485313/ https://lwn.net/Articles/485313/ landley <div class="FormattedComment"> No, int and long _aren't_ the same size on "most" architectures. They're the same size on 32 bit architectures, different on 64 bit. There's a standard for this, which Linux follows (and MacOS X, and most other unix variants):<br> <p> <a rel="nofollow" href="http://www.unix.org/whitepapers/64bit.html">http://www.unix.org/whitepapers/64bit.html</a><br> <p> Here's the rationale:<br> <p> <a rel="nofollow" href="http://www.unix.org/version2/whatsnew/lp64_wp.html">http://www.unix.org/version2/whatsnew/lp64_wp.html</a><br> <p> And here's the insane legacy reasons Windows decided to do something else instead:<br> <p> <a rel="nofollow" href="http://blogs.msdn.com/b/oldnewthing/archive/2005/01/31/363790.aspx">http://blogs.msdn.com/b/oldnewthing/archive/2005/01/31/36...</a><br> <p> Rob<br> </div> Mon, 05 Mar 2012 23:45:10 +0000 A sys_poll() ABI tweak https://lwn.net/Articles/484018/ https://lwn.net/Articles/484018/ dmarti Anyone who's actually using timeouts that long has probably already been tarred and feathered by their QA dept. How would you test them? Mon, 27 Feb 2012 19:47:51 +0000 A sys_poll() ABI tweak https://lwn.net/Articles/483885/ https://lwn.net/Articles/483885/ jzbiciak <div class="FormattedComment"> Well, lessee... 2 billion milliseconds is 2 million seconds. That's just over 23 days. Are there good reasons to have timeouts longer than that that aren't actually infinite?<br> </div> Sun, 26 Feb 2012 02:34:57 +0000