Remove all of our "to-do" items from the README.txt.

This commit was SVN r29424.

ompi/mca/btl/usnic/README.txt

@@ -247,63 +247,3 @@ of the large sends.  smalls would have to be paced pretty precisely to
 keep command queue empty enough and also beat out the large sends.
 send credits limit how many larges can be queued on the sender, but there
 could be many on the receiver
-
-
-
-
-
-
-
-
-======================================
-optim: round large buffer alloc up to cache line size?
-
-optim: ompi_btl_usnic_endpoint_send_segment() could have stuff
-    removed, moved into shadow of send.  ACK piggy-backing could be
-    broken in half, and some moved into shadow.
-
-optim: inline ompi_btl_usnic_endpoint_send_segment
-
-todo: move small send callback from progress to usnic_send
-
-todo: PUTs do not need fragment IDs - each chunk can be standalone, completion
-    is detected on sender by last byte ACKed, not on receiver
-
-todo: check warmup impact
-
-todo: improve sender lookup mechanism
-
-todo: RD WD size weirdness (e.g.:255 good, 256 bad)
-
-todo: do not IBV_SEND_SIGNALED every time
-
-todo: sf_size redundant with ack_bytes_left ?
-
-todo: BW hole in -np 32 Exchange on 32 nodes
-    dip right at eager limit
-    exchange wants different higher limit...
-
-todo: odd results with -np 16 Gather -npmin 16 on 16 nodes
-    something changes at 1024 bytes
-
-todo: test with packet loss/reording
-todo: get QA running IMB with .DCHECK 
-todo: do our own 256 process .DCHECK run on 32 nodes
-todo: registration cache w/o ummunotify
-todo: reg cache with ummunotify
-todo: thorough review of retransmission policy vs reordering
-todo: progression thread?
-todo: weird startup delay issue with periodic stats enabled 
-
-todo: maintaining verbs SG list and PML SG list in parallel is awkward
-    probably best to just fill in verbs SG list all at once at last possible
-    moment instead of piecemeal?  or always use verbs SG internally?
-    or use compile-time wizardry to make OMPI SG list and verbs SG list
-    be byte compatible?
-
-todo: update proc.c:match_modex() to use same kind of IP comparison as
-    in TCP BTL (i.e., subroutine-ize the TCP BTL comparison)
-
-todo: implement "wide match" btl_usnic_if_in|exclude (i.e., let a
-    specified mask of 10.0.0.0/8 match an interface with
-    10.20.0.0/16).