Re: replacing extent(9) with vmem(9): lessons learned

To: tech-kern%netbsd.org@localhost
Subject: Re: replacing extent(9) with vmem(9): lessons learned
From: David Young <dyoung%pobox.com@localhost>
Date: Thu, 3 Dec 2009 06:43:03 -0600

On Thu, Dec 03, 2009 at 01:32:00PM +0100, Christoph Egger wrote:
> Problem 4: vmem(9) does not allocate page aligned memory through kmem(9).
>       This is a problem e.g. for Xen where page-aligned memory is required for
>       the ring buffers. A workaround is to use uvm_km_alloc().

kmem(9) does not ask vmem(9) for page-aligned memory using
vmem_xalloc(9), although it could.  I don't see why that is a vmem(9)
problem.

Dave

-- 
David Young             OJC Technologies
dyoung%ojctech.com@localhost      Urbana, IL * (217) 278-3933

References:
- replacing extent(9) with vmem(9): lessons learned
  - From: David Young
- Re: replacing extent(9) with vmem(9): lessons learned
  - From: Christoph Egger

Prev by Date: Re: replacing extent(9) with vmem(9): lessons learned
Next by Date: Quirk WD_QUIRK_SPLIT_MOD15_WRITE
Previous by Thread: Re: replacing extent(9) with vmem(9): lessons learned
Next by Thread: Quirk WD_QUIRK_SPLIT_MOD15_WRITE
Indexes:

Home | Main Index | Thread Index | Old Index