en:pc:test_multiple_nvme_namespaces

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

en:pc:test_multiple_nvme_namespaces [2023-05-29 22:54]
Decomo created 		en:pc:test_multiple_nvme_namespaces [2023-05-31 09:08] (current)
Decomo
Line 98: Line 98:
 </code> </code>
  
-===== 名前空間の追加 =====+===== Add namespaces =====
  
 Any moment now, create new namespaces. Any moment now, create new namespaces.
Line 114: Line 114:
 | ''-c'', ''--ncap'' | Specify namespace capacity by block counts. The value must be equal to or less than '-s' specified value. If it is less than "nsze", the namespace will get over-provisioning. | | ''-c'', ''--ncap'' | Specify namespace capacity by block counts. The value must be equal to or less than '-s' specified value. If it is less than "nsze", the namespace will get over-provisioning. |
  
-作成した名前空間はコントローラにアタッチして初めて使えるようになる。+Added namespace will be available when it is attached to the controller.
  
 <code> <code>
Line 121: Line 121:
 </code> </code>
  
-同じ要領で、もう1つ名前空間を追加する。+Add one more namespace in the same way.
  
 <code> <code>
Line 131: Line 131:
 </code> </code>
  
-システムから''nvme0n1'', ''nvme0n2''として認識されていることが分かる。+It turns out the system recognises them as ''nvme0n1'' and ''nvme0n2''. 
 <code> <code>
 $ sudo nvme list $ sudo nvme list
Line 281: Line 282:
 </code>| </code>|
  
-===== UEFIやOSからの見え方 =====+===== How namespaces looks on UEFI or OS =====
  
 So actually let's get down to business. So actually let's get down to business.
  
-What NVMe devices can have multiple namespaces is good thing, but how are they after the second recognised by UEFI (BIOS) or OS?+What NVMe devices can have multiple namespaces is good thing, but how are they especially after the second recognised by UEFI (BIOS) or OS?
 The NVMe namespace is device divide function close to hardware layer, however, physical device as a PCIe device is still nothing but only one. The NVMe namespace is device divide function close to hardware layer, however, physical device as a PCIe device is still nothing but only one.
 I think software support by like a NVMe driver of a host system is one of important parts to work with the function. I think software support by like a NVMe driver of a host system is one of important parts to work with the function.
-It is a worrisome whether to support multiple namespaces or not especially in UEFI.+It is a worrisome whether to support multiple namespaces or not especially on UEFI.
  
 It's wonderful if the system can boot from arbitrary namespace, but there is no information on the net, so I actually check it out. It's wonderful if the system can boot from arbitrary namespace, but there is no information on the net, so I actually check it out.
Line 362: Line 363:
 Boot order has given priority to the second "UEFI OS", thus the Proxmox VE is launched as expected. That's impressive! Boot order has given priority to the second "UEFI OS", thus the Proxmox VE is launched as expected. That's impressive!
  
-===== 参考サイト =====+===== References =====
  
   * [[https://narasimhan-v.github.io/2020/06/12/Managing-NVMe-Namespaces.html|Managing Nvme Namespaces | Narasimhan V]]   * [[https://narasimhan-v.github.io/2020/06/12/Managing-NVMe-Namespaces.html|Managing Nvme Namespaces | Narasimhan V]]
  • en/pc/test_multiple_nvme_namespaces.txt
  • Last modified: 2023-05-31 09:08
  • by Decomo