Re: do i have to do virtualalloc, if i am accessing flash area outside of the NK?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Randal Leeson (randylrandyl_at_yahoo.com)
Date: 10/27/04 

Date: Wed, 27 Oct 2004 12:12:47 GMT

If the thread that will access the memory area is running in KERNEL
mode then it can access all of the memory mapped into the kernel
address space using the kernel mode addresses without using
VirtualAlloc/Copy.

If the image was built in full kernel mode then all threads will be
running in kernel mode and can use kernel mode addresses. Taking
advantage of this would only be recommened for a closed system and not
for a general purpose driver or BSP.

Randal Leeson

On Wed, 27 Oct 2004 16:52:54 +0800, "mobilevil" <mobilevil@mobile.com>
wrote:

>i am making a flash based block driver for wince 4.2
>it is working now but i wonder if the virutal alloc is really needed?
>in some cases i can write to it directly by pointer, without virual alloc.
>currently i am allocating 4M at a time, and switch to another 4M when
>needed.
>

Relevant Pages

  • [Q]insmod and User mode address memory allocation?
    ... Can anybody tell me why insmod allocates a memory area in the User ... A user can link a module into the running kernel by executing the ... Initializes the fields of the module object at the beginning of the ...
    (comp.os.linux.embedded)
  • Re: system slowdown - vnode related
    ... Does the number of vnodes shoot up when 310.locate ... to 0 to disable namecache entirely and see if your problem completely ... I've been reading some of the kernel source and tracking down ... There seems to be a senario where the memory area for namecache ...
    (freebsd-stable)
  • Re: experienced opinions
    ... Rainer Weikusat wrote: ... select loops who didn't understand that the information they passed ... into the kernel is no longer contained in the memory area they wrote ...
    (comp.unix.programmer)
  • Re: [PATCH -mm -v5 0/3] i386/x86_64 boot: 32-bit boot protocol
    ... and memory area used during kernel boot through bootmem allocator? ... You can't solve this through bootmem because x86-64 allocates memory ... non-conflict memory area through e820 map. ... Because setup data is allocated by bootloader or kernel 16-bit setup ...
    (Linux-Kernel)