Hacker Blogs
Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #1838

L

locklessinc.com

Company blog · locklessinc.com/articlesprogrammingsystems

locklessinc.com is the company blog at locklessinc.com, writing about programming and systems. Since 2010, 39 different Hacker News readers have linked it 45 times, most often “Why Lisp Failed. (2009)”. It has a working feed you can follow.

Visit the blog
45mentions?
39HN people?
2010–2021first – last linked?
Links on Hacker News per year · peak 8 in 2013

Too few sampled comments (13) to say how often HN recommends it.?

Why HN links it

Lockless Inc's articles cover low-level C and C++ topics: tricky C semantics, intrusive lists, compiler vectorization and memory allocator benchmarks. HN readers link them as technical references.

Summarised by Claude from a sample of 13 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Lockless Inc is the developer of the world's fastest memory allocator. Use it to increase the performance of your applications.

Most-linked posts?

  1. /benchmarks_allocator.shtml
    5 people · 5 mentions · first linked 2012-03-26
  2. Why Lisp Failed. (2009)
    4 people · 4 mentions · first linked 2011-08-07
  3. Auto-vectorization with gcc 4.7
    3 people · 3 mentions · first linked 2012-05-22
  4. Why Lisp Failed (2010)
    3 people · 3 mentions · first linked 2018-02-01
  5. Doubly Linked Lists in C
    2 people · 2 mentions · first linked 2013-02-21
  6. Optimization Tricks used by the Lockless Memory Allocator
    2 people · 2 mentions · first linked 2011-11-16
  7. /articles/
    2 people · 2 mentions · first linked 2019-07-06
  8. Branchfree Saturating Arithmetic in C
    2 people · 2 mentions · first linked 2010-12-23
  9. The TCP/IP Checksum (2012)
    2 people · 2 mentions · first linked 2021-11-27
  10. Mutexes and Condition Variables using Futexes
    2 people · 2 mentions · first linked 2010-07-29

What Hacker News says?

  1. rramadass · 2019-07-06Recommends
    This quiz wasn't illuminating at all. You generally start with assuming and validating a "C Datatype Model" i.e. ILP32/LP64 etc. for your system. Once you know that, these questions are easily answered. If you want to see some real tricky C code, see some of the articles here: https://locklessinc.com/articles/

    Comment linking /articles/

    on “So you think you know C? (2016)”
  2. tosh · 2019-07-07

    Submitted Why Lisp Failed (2010) as a story · 121 points

    HN discussion
  3. gsg · 2013-12-02Recommends
    You might find http://www.locklessinc.com/articles/dlist/ interesting: it describes a (perhaps excessively) clever way to do intrusive lists that gives type checking. (Unfortunately it does rely on `typeof`, an extension.)

    Comment linking /articles/dlist/

    on “How to Make a Computer Operating System in C/C++”
  4. jcsalterego · 2011-11-16

    Submitted Optimization Tricks used by the Lockless Memory Allocator as a story · 60 points

    HN discussion
  5. danbolt · 2016-01-27
    The mindshare bit is an interesting one. I once read an article [1] that argued Lisp did not reach the same level of industrial popularity as other programming languages due to the fact that Lisp enables you to program in a lot of different ways for different reasons. I'm admittedly not very familiar with Lisp, and I don't know if I fully agree with the article, but it made me wonder if ease-of-collaboration can be…

    Comment linking /articles/why_lisp_failed/

    on “My Reaction to React”
  6. skorks · 2010-03-20

    Submitted 256 Bit Arithmetic as a story · 22 points

    HN discussion
  7. throwaway4891a · 2016-11-15
    See also: - http://locklessinc.com/benchmarks_allocator.shtml ($, use as a minimum performance target) - http://www.nedprod.com/programs/portable/nedmalloc/ - http://phk.freebsd.dk/pubs/malloc.pdf [PDF] (phkmalloc) - https://github.com/gperftools/gperftools (tcmalloc) - https://github.com/ivmai/bdwgc/blob/master/malloc.c - https://github.com/jemalloc/jemalloc - http://gee.cs.oswego.edu/dl/html/malloc.html (dlmalloc)

    Comment linking /benchmarks_allocator.shtml

    on “Malloc Challenge”
  8. skorks · 2010-02-08

    Submitted Spinlocks and Read-Write Locks as a story · 10 points

    HN discussion
  9. throwawayaway · 2015-12-21
    Wow! Want to do a full disclosure? Your papers were very valuable while doing my undergraduate study. Is Hoard neck and neck with jemalloc and lockless' allocator nowadays? http://locklessinc.com/benchmarks_allocator.shtml

    Comment linking /benchmarks_allocator.shtml

    on “SuperMalloc: A Super Fast Multithreaded Malloc for 64-bit Machines”
  10. srsamarthyam · 2013-02-21

    Submitted Mocking Functions in C as a story · 5 points

    HN discussion
  11. chuckcode · 2014-12-23
    Completely agree. Restrict keyword can free up the compiler to vectorize a lot of code with sse and avx on intel chips. [1] http://locklessinc.com/articles/vectorize/ [2] http://stackoverflow.com/questions/1965487/does-the-restrict...

    Comment linking /articles/vectorize/

    on “Popular Myths about C++, Part 3”
  12. silentbicycle · 2012-05-22

    Submitted Auto-vectorization with gcc 4.7 as a story · 5 points

    HN discussion
  13. runn1ng · 2019-07-07
    Add (2009) to this article. https://locklessinc.com/articles/

    Comment linking /articles/

    on “Why Lisp Failed (2010)”
  14. adgasf · 2018-11-12

    Submitted Why Lisp Failed as a story · 4 points

    HN discussion
  15. ramchip · 2014-06-21
    > all decent C compilers can easily and robustly generate such code From what I've seen auto-vectorization is anything but robust, often you need non-portable annotations to get anything decent. See e.g.: http://locklessinc.com/articles/vectorize/ where there's an interesting case where using "if" instead of a ternary operator is enough to prevent optimization.

    Comment linking /articles/vectorize/

    on “C++ design goals in the context of Rust (2010)”
  16. panic · 2015-03-06

    Submitted Doubly Linked Lists in C as a story · 4 points

    HN discussion
  17. vardump · 2015-06-25
    For those who still think manual memory management and especially malloc and free are fast, check glibc implementation. https://fossies.org/dox/glibc-2.21/malloc_8c_source.html#l02... Also see this benchmark between different, faster allocators: http://locklessinc.com/benchmarks_allocator.shtml The extra work doesn't end at allocation. When you actually implement a concurrent system, you'll usually end up having cor…

    Comment linking /benchmarks_allocator.shtml

    on “Ark – A modern systems programming language”
  18. X4 · 2011-11-15

    Submitted Lockless Inc. High-Performance Memory Allocator (Now Open Source GPL 3.0) as a story · 4 points

    HN discussion
  19. chuckcode · 2015-06-07
    I've found measuring memory usage with STL containers to be difficult as they have their own allocator and unless you're using reserve() often end up allocating extra space for things. Dr Dobbs had an interesting article a long time ago around optimizing allocators [1] and also memory management was one of the main reasons that Electronic Arts rolled their own variant of the STL [2]. I use a lot of STL for convenien…

    Comment linking /benchmarks_allocator.shtml

    on “Graph Engine vs. C++ unordered_map: memory consumption test, Part 2”
  20. raganwald · 2010-04-26

    Submitted Weird Binary as a story · 4 points

    HN discussion
  21. avdicius · 2015-04-24
    Thank you very much for your review. - I have a TATAS lock implementation elsewhere: https://github.com/ademakov/MainMemory/blob/master/src/base/... Could add it to Evenk as well. - Exchanged value in FutexLock is not discarded, it is used in the conditions of the `if` and `while` statements. In both cases the returned value of 0 means that we've got the lock and the next thing executed will be the `break` statement…

    Comment linking /articles/mutex_cv_futex/

    on “Show HN: Evenk C++ concurrency library”
  22. Kristine1975 · 2017-03-02

    Submitted Branchfree Saturating Arithmetic in C as a story · 3 points

    HN discussion
  23. vgnet · 2012-03-26
    There's a very interesting comparison between libumem (mtmalloc) and Hoard at http://www.oracle.com/technetwork/articles/servers-storage-d... (HN link: https://news.ycombinator.com/item?id=3755621 ). How do you view this class of allocators to tcmalloc, jemalloc, ptmalloc3, etc., specially in the concurrent multi-cpu scenario? Here's what I'll be reading on allocators tonight, any further suggestions (following all…

    Comment linking /benchmarks_allocator.shtml

    on “The Hoard Memory Allocator”
  24. behnamoh · 2016-09-23

    Submitted Why Lisp Failed. (2009) as a story · 3 points

    HN discussion
  25. ramchip · 2010-03-03Recommends
    Interesting! I found a good explanation at http://locklessinc.com/articles/flexible_lists_in_cpp/ I do wonder how they could have missed the obviousness of it. Or maybe it's just the shotgun approach to patent trolling.

    Comment linking /articles/flexible_lists_in_cpp/

    on “Linked List Patent”
  26. redDragon · 2012-11-07

    Submitted Optimizing the TCP/IP Checksum as a story · 3 points

    HN discussion
  27. signa11 · 2021-11-28

    Submitted The TCP/IP Checksum as a story · 2 points

    HN discussion
  28. todsacerdoti · 2021-11-27

    Submitted The TCP/IP Checksum (2012) as a story · 2 points

    HN discussion
  29. mudbone · 2018-02-01

    Submitted Why Lisp failed as a story · 2 points

    HN discussion
  30. AndreyKarpov · 2017-02-20

    Submitted Creating a Fast Hash Function as a story · 2 points

    HN discussion

Search all of HN for locklessinc.com

Linked by the same people?