>> Required XFS bits:
>> 2.4 2.4-ac 2.5
>> --------------------------------------------------------------------
>> buffer writeback through ->writepage - - x (1)
>> mapping of arbitrary pages into KVA - - x
>> kmem_cache_size() x x x
>> -funsigned-char friendly spin_is_locked() x - (2) x
>> ->alloc_inode/->destroy_inode methods - - x
>> iget_locked() - - x
>> lockless generic_file_write() - - x
>> find_or_create_page() exported/inline - - x
>> mark_page_accessed exported - - -
>> PF_FTRANS flag for task_struct - - -
>> generic_file_direct_IO fixes - - - (3)
>> additional exports - - - (4)
>> XFS filesystem code - - -
>> (1) Andrew Morton's buffer layer rewrite provides equivalent functionality
>> (2) Alan backed it out. Needed for debug builds currently.
>> (3) Not needed in 2.5, we use the less picky generic O_DIRECT code
>> (4) Not needed/already exported in 2.5
Does that mean for 2.5 once the mark_page_accessed and PG_TRANS issues are
resolved, the whole XFS filesystem is ready to go in with _no_ more massaging?
Or does it mean that those 2 have to go in plus a lot of other massaging to the
XFS filesystem code before it gets officially incorporated?
Just curious
Greg
========
Greg Freemyer
Internet Engineer
Deployment and Integration Specialist
Compaq ASE - Tru64 v4, v5
Compaq Master ASE - SAN Architect
The Norcross Group
www.NorcrossGroup.com
|