Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Extended\s+attribute\s+caching\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Extended\s+attribute\s+caching\s*$/: 9 ]

Total 9 documents matching your query.

1. Extended attribute caching (score: 1): Author:; Date: Wed, 29 Oct 2003 11:09:29 -0800 (PST); I wanted to find out what performance impact setting/getting extended attributes would have on file I/O on XFS. Therefore for every file I/O I set a 4 byte extended attribute in "user" name space. T; /archives/xfs/2003-10/msg00238.html (7,973 bytes)
2. Re: Extended attribute caching (score: 1): Author:; Date: 29 Oct 2003 13:32:17 -0600; Stat is a read only call, setting an extended attribute does a transaction. There may not be disk I/O on all calls, but there will be disk writes involved. Caching is not the issue, you are changing; /archives/xfs/2003-10/msg00240.html (9,300 bytes)
3. Re: Extended attribute caching (score: 1): Author:; Date: Wed, 29 Oct 2003 13:19:06 -0800 (PST); Thanks for the response. Assuming there is sufficient space in the inode, is it guaranteed that the extended attribue will be stored in the inode and hence in the inode cache ? == -- Ravi Wijayaratn; /archives/xfs/2003-10/msg00245.html (9,790 bytes)
4. Extended attribute caching (score: 1): Author: >; Date: Wed, 29 Oct 2003 11:09:29 -0800 (PST); I wanted to find out what performance impact setting/getting extended attributes would have on file I/O on XFS. Therefore for every file I/O I set a 4 byte extended attribute in "user" name space. T; /archives/xfs/2003-10/msg00522.html (7,973 bytes)
5. Re: Extended attribute caching (score: 1): Author: >; Date: 29 Oct 2003 13:32:17 -0600; Stat is a read only call, setting an extended attribute does a transaction. There may not be disk I/O on all calls, but there will be disk writes involved. Caching is not the issue, you are changing; /archives/xfs/2003-10/msg00524.html (9,300 bytes)
6. Re: Extended attribute caching (score: 1): Author: >; Date: Wed, 29 Oct 2003 13:19:06 -0800 (PST); Thanks for the response. Assuming there is sufficient space in the inode, is it guaranteed that the extended attribue will be stored in the inode and hence in the inode cache ? == -- Ravi Wijayaratn; /archives/xfs/2003-10/msg00529.html (9,790 bytes)
7. Extended attribute caching (score: 1): Author: Ravi Wijayaratne <ravi_wija@xxxxxxxxx>; Date: Wed, 29 Oct 2003 11:09:29 -0800 (PST); Hi, I wanted to find out what performance impact setting/getting extended attributes would have on file I/O on XFS. Therefore for every file I/O I set a 4 byte extended attribute in "user" name space; /archives/xfs/2003-10/msg00806.html (7,988 bytes)
8. Re: Extended attribute caching (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: 29 Oct 2003 13:32:17 -0600; Stat is a read only call, setting an extended attribute does a transaction. There may not be disk I/O on all calls, but there will be disk writes involved. Caching is not the issue, you are changing; /archives/xfs/2003-10/msg00808.html (9,368 bytes)
9. Re: Extended attribute caching (score: 1): Author: Ravi Wijayaratne <ravi_wija@xxxxxxxxx>; Date: Wed, 29 Oct 2003 13:19:06 -0800 (PST); Steve Thanks for the response. Assuming there is sufficient space in the inode, is it guaranteed that the extended attribue will be stored in the inode and hence in the inode cache ? == -- Ravi Wijay; /archives/xfs/2003-10/msg00813.html (9,864 bytes)

Current List: 1 - 9
Page: [1]