Jeff, remember I asked you not to merge the UBD rewrite for now? Well, I found
one more (and bigger) reason for it, though I don't understand it fully.
Quoting from Arjan Van der Ven, "How not to write kernel driver":
In the write path of a filesystem, using
GFP_KERNEL or GFP_ATOMIC will lead to deadlocks
eventually. [...] GFP_NOFS is there for a reason, as is GFP_NOIO for block
device drivers.
Though there's no explaination of this, I can guess that GFP_KERNEL could
cause the kernel to enter the same (or another, but that shouldn't matter)
block device to free some memory. Not sure what's the problem with GFP_ATOMIC
though.
However, GFP_NO{FS,IO} both imply !ATOMIC (they include __GFP_WAIT), so we
cannot use any of them for our purposes.
Which means that we _must_ ask for help from somebody else.
Anyhow, before merging the patches I'd _really_ like if they were reviewed by
somebody as Jens Axboe or the such, afterwards merged to -mm, and only after
that merged into mainline.
Please, send some feedback on this email as soon as you read - think to
replacing UDP with TCP, ok ;-) ?
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
User-mode-linux-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
