| @@ -1,14 +1,14 @@ | | | @@ -1,14 +1,14 @@ |
1 | $NetBSD: storage,v 1.25 2018/04/12 19:11:35 jdolecek Exp $ | | 1 | $NetBSD: storage,v 1.26 2018/04/12 19:12:25 jdolecek Exp $ |
2 | | | 2 | |
3 | NetBSD Storage Roadmap | | 3 | NetBSD Storage Roadmap |
4 | ====================== | | 4 | ====================== |
5 | | | 5 | |
6 | This is a small roadmap document, and deals with the storage and file | | 6 | This is a small roadmap document, and deals with the storage and file |
7 | systems side of the operating system. It discusses elements, projects, | | 7 | systems side of the operating system. It discusses elements, projects, |
8 | and goals that are under development or under discussion; and it is | | 8 | and goals that are under development or under discussion; and it is |
9 | divided into three categories based on perceived priority. | | 9 | divided into three categories based on perceived priority. |
10 | | | 10 | |
11 | The following elements, projects, and goals are considered strategic | | 11 | The following elements, projects, and goals are considered strategic |
12 | priorities for the project: | | 12 | priorities for the project: |
13 | | | 13 | |
14 | 1. Improving iscsi | | 14 | 1. Improving iscsi |
| @@ -195,27 +195,27 @@ on laptops in many circumstances. | | | @@ -195,27 +195,27 @@ on laptops in many circumstances. |
195 | | | 195 | |
196 | 6. Finish tls-maxphys | | 196 | 6. Finish tls-maxphys |
197 | --------------------- | | 197 | --------------------- |
198 | | | 198 | |
199 | The tls-maxphys branch changes MAXPHYS (the maximum size of a single | | 199 | The tls-maxphys branch changes MAXPHYS (the maximum size of a single |
200 | I/O request) from a global fixed constant to a value that's probed | | 200 | I/O request) from a global fixed constant to a value that's probed |
201 | separately for each particular I/O channel based on its | | 201 | separately for each particular I/O channel based on its |
202 | capabilities. Large values are highly desirable for e.g. feeding large | | 202 | capabilities. Large values are highly desirable for e.g. feeding large |
203 | disk arrays and SSDs, but do not work with all hardware. | | 203 | disk arrays and SSDs, but do not work with all hardware. |
204 | | | 204 | |
205 | The code is nearly done and just needs more testing and support in | | 205 | The code is nearly done and just needs more testing and support in |
206 | more drivers. | | 206 | more drivers. |
207 | | | 207 | |
208 | - On October 2018 jdolecek re-synced the branch, intention is to wrap | | 208 | - On October 2017 jdolecek re-synced the branch, intention is to wrap |
209 | this up for future netbsd-9 | | 209 | this up for future netbsd-9 |
210 | - Contact jdolecek or tls for further information. | | 210 | - Contact jdolecek or tls for further information. |
211 | | | 211 | |
212 | | | 212 | |
213 | 7. nvme suppport | | 213 | 7. nvme suppport |
214 | ---------------- | | 214 | ---------------- |
215 | | | 215 | |
216 | nvme ("NVM Express") is a hardware interface standard for PCI-attached | | 216 | nvme ("NVM Express") is a hardware interface standard for PCI-attached |
217 | SSDs. NetBSD now has a driver for these. | | 217 | SSDs. NetBSD now has a driver for these. |
218 | | | 218 | |
219 | Driver is now MPSAFE and uses bufq fcfs (i.e. no disksort()) already, | | 219 | Driver is now MPSAFE and uses bufq fcfs (i.e. no disksort()) already, |
220 | so the most obvious software bottlenecks were treated. It still needs | | 220 | so the most obvious software bottlenecks were treated. It still needs |
221 | more testing on real hardware, and it may be good to investigate some further | | 221 | more testing on real hardware, and it may be good to investigate some further |