Contents of /alx-src/trunk/kernel26-alx/linux/Documentation/aoe/todo.txt
Parent Directory
| 
Revision Log
Revision 628 -
(show annotations)
(download)
Wed Mar 4 10:48:58 2009 UTC (15 years, 1 month ago) by niro
File MIME type: text/plain
File size: 788 byte(s)
Wed Mar 4 10:48:58 2009 UTC (15 years, 1 month ago) by niro
File MIME type: text/plain
File size: 788 byte(s)
import linux sources based on 2.6.12-alx-r9: -using linux-2.6.12.6 -using 2.6.12-ck6 patch set -using fbsplash-0.9.2-r3 -using vesafb-tng-0.9-rc7 -using squashfs-2.2 -added cddvd-cmdfilter-drop.patch as ck dropped it -added via-epia-dri (cle266) patch -added zd1211-svn-32 wlan driver (http://zd1211.ath.cx/download/) -added debian patches to zd1211 for wep256 etc
| 1 | There is a potential for deadlock when allocating a struct sk_buff for |
| 2 | data that needs to be written out to aoe storage. If the data is |
| 3 | being written from a dirty page in order to free that page, and if |
| 4 | there are no other pages available, then deadlock may occur when a |
| 5 | free page is needed for the sk_buff allocation. This situation has |
| 6 | not been observed, but it would be nice to eliminate any potential for |
| 7 | deadlock under memory pressure. |
| 8 | |
| 9 | Because ATA over Ethernet is not fragmented by the kernel's IP code, |
| 10 | the destructore member of the struct sk_buff is available to the aoe |
| 11 | driver. By using a mempool for allocating all but the first few |
| 12 | sk_buffs, and by registering a destructor, we should be able to |
| 13 | efficiently allocate sk_buffs without introducing any potential for |
| 14 | deadlock. |