Re: Identifying disks by name

On 22 jun 2011, at 20:53, Kenneth R Westerback wrote: > On Wed, Jun 22, 2011 at 06:48:14PM +0200, Wouter Coene wrote: >> The patch below builds on the disk UID code to implement disk names. Disk >> names must match [a-zA-Z0-9_]{1,10} and are stored encoded as 6 bits per >&g

Identifying disks by name

Hi all, The patch below builds on the disk UID code to implement disk names. Disk names must match [a-zA-Z0-9_]{1,10} and are stored encoded as 6 bits per character into the disklabel UID field. With this patch, you can use disk names in /etc/fstab: bootdisk.a / ffs rw 1 1 And with every

Re: uvm(9) clarifications wrt. uvm_km_alloc() / uvm_km_free()

According to Ariane van der Steldt (ari...@stack.nl): > On Thu, Dec 09, 2010 at 10:32:57PM +0100, Wouter Coene wrote: > > + addr = uvm_km_kmemalloc(kernel_map, NULL, PAGE_SIZE, > > + UVM_KMF_CANFAIL | UVM_KMF_ZERO); > > If you specify NULL a

Re: uvm(9) clarifications wrt. uvm_km_alloc() / uvm_km_free()

On 9 dec 2010, at 08:32, Ariane van der Steldt wrote: > I'm not yet convinced. What are you trying to do? Pretty much as I described: I allocate kernel memory through uvm_km_kmemalloc() from kernel_map, and then free it through uvm_km_free(), returning it to the kernel_map. The code I'm working o

uvm(9) clarifications wrt. uvm_km_alloc() / uvm_km_free()

ct? And if so, any chance this could go in? Regards, Wouter Coene

mmap()'ing non-vnode files

e that doesn't break source-compatibility with Linux's KVM too much)? Thanks in advance for any help, Wouter Coene