Re: Graceful failure instead of panicking in kmem_malloc

number 8? On Jan 9, 2008 9:30 AM, Mike <[EMAIL PROTECTED]> wrote: > Bharma Ji wrote: > > Is there any way to make the system log and then gracefully shut off > instead > > of panicking? > > Is there any way to make the system log and then gracefully shut off while > gu

Re: Graceful failure instead of panicking in kmem_malloc

- if there is any way already discussed or standardized to make the system handle failures gracefully On Jan 8, 2008 4:30 PM, Kris Kennaway <[EMAIL PROTECTED]> wrote: > Bharma Ji wrote: > > In FreeBSD 6_2, if kmem_malloc is unable to find space it panics. The > > relevant

Graceful failure instead of panicking in kmem_malloc

In FreeBSD 6_2, if kmem_malloc is unable to find space it panics. The relevant code is in vm_kern.c if ((flags & M_NOWAIT) == 0) panic("kmem_malloc(%ld): kmem_map too small: %ld total allocated", (long)size, (long)map->size); Is there any

Is there any way to avoid copy between the kernel and userland

Hi I am looking for any FreeBSD facility that will allow a userland process to pass data to the kernel without doing a copyin or copyout e.g. using a shared data structure (queue? ) for example? Any pointers will be useful Thanks ___ freebsd-hackers@free

differences between M_CACHE, M_DEVBUF, M_TEMP

Hi I am trying to understand the difference in these three different memories. Code comments in kern_malloc.c says that M_DEVBUF should be used for device driver. I didn't however see any major difference between the three memories. Can a device theoretically take up memory from M_TEMP (or M_CACH

how to find the physical memory allocated to the kernel

Hi Is there any way to determine the physical memory(not the virtual address space) being allocated to the kernel at any instant? The overall problem is that once I allocate say 512 MB to the kernel (virutal address space) through the config file at compile time, I want to figure out how much of t

memory allocation / deallocation within the kernel

I am trying to understand the impact of memory allocation / deallocation within the kernel. As I understand a) Kernel memory is not pageable ie the one you get from using kernel malloc(there may be exceptions) b) Does this imply that if I have 1 GB of RAM - then I cannot reserve more than 1 GB of

How to pin a userland page in memory(avoid copyin and copyout)

Hi I am trying to explore the option avoiding copyin and copyout when mode switches from user to kernel and vice versa. One way to achieve this, as I understand, is to make the memory address (which contain the data to be copied) non pageable. Then just pass the addresses to the kernel and the data