User: Password:
|
|
Subscribe / Log in / New account

Avoiding memory-allocation deadlocks

Avoiding memory-allocation deadlocks

Posted Apr 24, 2014 6:44 UTC (Thu) by kevinm (guest, #69913)
Parent article: Avoiding memory-allocation deadlocks

I strongly suspect that the reason the "new" GFP_IO was an allocation flag rather than a process flag is that a given piece of code should generally know exactly what locks may be held when it is called (hence it knows whether to supply GFP_IO or not), but you cannot expect any particular piece of code to know whether it's being called within a memory allocation path or not.


(Log in to post comments)


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds