Post ApVsfQMJr5FBHZcRlI by torvalds@social.kernel.org
 (DIR) More posts by torvalds@social.kernel.org
 (DIR) Post #Alr4Yvvis8EtG4CQrY by sima@chaos.social
       2024-09-10T08:39:19Z
       
       0 likes, 0 repeats
       
       @lina @gregkh I just thought it's general protection fault, misspelled, and made no sense. not the first acronym I'll never understand, so just shrugged for the past few decades of looking at kernel code
       
 (DIR) Post #Alr4ZwsiosGwV0HQQq by sima@chaos.social
       2024-09-10T08:30:05Z
       
       0 likes, 1 repeats
       
       kangrejos in copenhagen was great, but the absolute 🤯 moment was when I learned that GFP_ stands for get_free_pagesI had no idea. and @gregkh next to me had the same https://xkcd.com/1053/ experience#kernel
       
 (DIR) Post #Alr5PyJqihD612m7xQ by ljs@social.kernel.org
       2024-09-10T08:49:00.707033Z
       
       1 likes, 0 repeats
       
       @sima @gregkh lol I'm so glad I got that right in the book.You'd think Greg would suggest 'Greg's F-ing Pages'
       
 (DIR) Post #AlswH0OH8ehYYwPmyW by gregkh@social.kernel.org
       2024-09-11T06:03:11.510732Z
       
       0 likes, 0 repeats
       
       @sima Right after this happened, I went and checked the LDD3 book, and yes it says this in the chapter about memory:         (internally performed by calling, eventually, __get_free_pages, which is the source of the GFP_ prefix))So I have no excuse for not remembering this either...
       
 (DIR) Post #ApVsfQMJr5FBHZcRlI by torvalds@social.kernel.org
       2024-09-11T18:43:08.162785Z
       
       1 likes, 0 repeats
       
       @gregkh @sima “eventually calling __get_free_pages”?You have to realize that when the GFP_xyz flags were introduced - back in 1992 - “get_free_page()” was the only way to allocate memory. So “GFP” wasn’t some odd internal thing. There was nothing else (ok, there was a very simply malloc() library on top of that “you can free and allocate one page” mode).No “eventually” about it. It was the thing.