Bakeathon 2007 Issues List

From Linux NFS

(Difference between revisions)
Jump to: navigation, search
Line 19: Line 19:
* Layout driver API and layout driver callback API needs to be streamlined and optimized
* Layout driver API and layout driver callback API needs to be streamlined and optimized
-> Avoid having layout driver calling NFS common code directly, it should use the layout driver callback API.
-> Avoid having layout driver calling NFS common code directly, it should use the layout driver callback API.
 +
* Can we flush data before calling layout commit?  Could be a big performance hit if not.

Revision as of 17:05, 11 October 2007

  • Complete server export getdeviceinfo/getdevicelist implementation [Marc/Dean]
  • Number of sessions slots hardcoded to be number of rpc slots. Need ability to dynamically change this value. rpc_slots is ceiling on sessions_slots. Dynamic slot allocation on client and server. [Rahul]
  • Sessions priority on sessions slot table. Change to use priority wait queue for slot table. (will do fair scheduling) []
  • Session/sunrpc retry behavior [?]
  • Session interupt issues [?]
  • Incremental sessionid creation issues [Marc]
  • Client layout syncronization issues [Benny]
  • 2.6.18 client port to 2.6.23 [Andy, Ricardo]
  • Managing layout segment (alloc/inject layout) [Andy, Benny]
  • Layout device/lease []
  • Delegations and Layouts []
  • Continue to use devicelist on mount? []
  • MDS/DS I/O syncronization, need to determine if 'commit' needs to be sent to data servers and/or MDS []

->

  • Layoutget timing [Andy pay attention as code ported forward]
-> Put when write/read chunk size determined (nfs_pageio_init_write/read)
  • Asyncronous layoutget [Future Work, Requires more investigation/justification]
  • Server 4.1 replay cache [Extra 4.1 correctness work]
  • Layout driver API and layout driver callback API needs to be streamlined and optimized

-> Avoid having layout driver calling NFS common code directly, it should use the layout driver callback API.

  • Can we flush data before calling layout commit? Could be a big performance hit if not.
Personal tools