- Community Home
- >
- HPE Community, Taiwan
- >
- HP-UX
- >
- 系統管理
- >
- async i/o and sync i/o
系統管理
1753943
會員
8461
線上
108811
解決方案
論壇
類別
Company
Local Language
返回
論壇
討論平台
返回
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
部落格
信息
社區語言
語言
論壇
部落格
文章選項
- 訂閱此主題的RSS 提要
- 將此主題標記為未讀
- 將主題標記為已讀
- 將主題在本帳號置頂
- 標示為書籤
- 訂閱此主題
- 列印此頁
- 將文章標記為未讀
- 標示為書籤
- 訂閱此主題
- 靜音
- 訂閱此主題的RSS 提要
- 高亮顯示此文章
- 列印此文章
- 提報不當內容
在 09-09-2004 12:01 PM
在 09-09-2004 12:01 PM
async i/o and sync i/o
我看到一篇文章說
HP-UX 11i Online JFS file system today only support synchronous IO.
請問async io and sync io 的比較跟優缺點
這跟disk storage 的cache 有關嗎
HP-UX 11i Online JFS file system today only support synchronous IO.
請問async io and sync io 的比較跟優缺點
這跟disk storage 的cache 有關嗎
2則回覆 2
- 將文章標記為未讀
- 標示為書籤
- 訂閱此主題
- 靜音
- 訂閱此主題的RSS 提要
- 高亮顯示此文章
- 列印此文章
- 提報不當內容
在 09-09-2004 01:58 PM
在 09-09-2004 01:58 PM
async i/o and sync i/o
Hi :
這個問題可分兩個方向來看:
1. For block device, that is buffer cached I/O.
async I/O -
open() file without O_SYNC flag set,
As many as write() can be fired without having to wait for
them to complete.
Good performance, weak data integrity.
Sync I/O -
The next write() must wait the first write() complete
and then which can continue to go on.
Good data integrity but weak performance.
2. For raw device, that is non buffer cached I/O.
Sync I/O -
Normally, All I/O on raw device are synchronous,
The next write() must wait the first write() complete
and then which can continue to go on, because this is
no buffer cache there.
Async I/O -
Special driver give buufer-cache-like features on
raw I/O devices. Which let the user can fire more I/O
at the same time.
Such as Sybase achieves by using the HP async driver.
and the Oracle application does its own queueing of what
the OS sees as raw I/O requests, but which users might call
multiple async I/Os, even though they are using the raw device.
The buffer cache used for block device is on system main memory.
Which is not relative to cache size of storage.
PS, I try to make the explan in Chinese but .... Sorry about this.
Hope my explan is clear enough.
..
.
這個問題可分兩個方向來看:
1. For block device, that is buffer cached I/O.
async I/O -
open() file without O_SYNC flag set,
As many as write() can be fired without having to wait for
them to complete.
Good performance, weak data integrity.
Sync I/O -
The next write() must wait the first write() complete
and then which can continue to go on.
Good data integrity but weak performance.
2. For raw device, that is non buffer cached I/O.
Sync I/O -
Normally, All I/O on raw device are synchronous,
The next write() must wait the first write() complete
and then which can continue to go on, because this is
no buffer cache there.
Async I/O -
Special driver give buufer-cache-like features on
raw I/O devices. Which let the user can fire more I/O
at the same time.
Such as Sybase achieves by using the HP async driver.
and the Oracle application does its own queueing of what
the OS sees as raw I/O requests, but which users might call
multiple async I/Os, even though they are using the raw device.
The buffer cache used for block device is on system main memory.
Which is not relative to cache size of storage.
PS, I try to make the explan in Chinese but .... Sorry about this.
Hope my explan is clear enough.
..
.
- 將文章標記為未讀
- 標示為書籤
- 訂閱此主題
- 靜音
- 訂閱此主題的RSS 提要
- 高亮顯示此文章
- 列印此文章
- 提報不當內容
在 09-09-2004 02:52 PM
在 09-09-2004 02:52 PM
async i/o and sync i/o
基本上, disk storage 的 cache 是 contoller 在控制的, 可以設成 write back or write through, 跟 sync/async disk io 無關.
以上表述為作者個人觀點,不代表惠普公司,使用本網站,請遵守網站使用規則和條款
© 版权所有 2024 慧与发展有限责任合伙企业