02-27-2010
I didn't study OS design, but shouldn't the malloc() function be part of the C library, not the kernel?
That aside, I'd write it in assembly language (after all, it's pretty CPU specific, and might even be time-critical). Also, it might help flipping through Tannenbaums
Operating Systems Design and Implementation, as I'm sure that there's some information in there.
Minix is the implementation of the theories put forth there.
10 More Discussions You Might Find Interesting
1. Programming
1 . Thanks everyone who read the post.
2 . the programe is that :
#include <stdio.h>
#include <string.h>
void do_it(char *p)
{
p = (char *) malloc(100);
(void )strcpy(p,"1234");
}
int main(void)
{
char *p;
do_it(p);
(void )printf("p = %s \n",p); (1 Reply)
Discussion started by: chenhao_no1
1 Replies
2. Programming
hello sir
since by mentioning a integer pointer and storing the integers
by incrementing the pointer value
then what is the purpose of malloc?
u can decalre it as
in t *p;
several integers can be stored by incrementing the value of p,
hence what is the diffrence between this... (2 Replies)
Discussion started by: rajashekaran
2 Replies
3. Programming
Hello
This is a simple program i carried out in my machine
i dont know how it is working
#include<alloc.h>
#include<stdio.h>
mian()
{
int *p,j;
p= (int*)malloc(1);
for(j=1;j<=580;j++)
{
*p=j;
++p;
}
p=p-580;
for(j=1;j<=580;j++)
{
printf("%d",*p);
} (7 Replies)
Discussion started by: rajashekaran
7 Replies
4. Programming
Hi All!
Does some one know I am under UNIX system can not allocate more then 1 Mb memory? It broke program down.
Any information would be greatly appreciated.
Thanks. (2 Replies)
Discussion started by: prodigal
2 Replies
5. Programming
Hi!
I hope this is the correct forum to post the question even if I'm a newbie...
I am a C-newbie (and really on the edge to be a C-addict ;) ) and have a question.
When should I use malloc?
To state it differently, when should I NOT use malloc?
For instance, if I have an array of... (5 Replies)
Discussion started by: Tonje
5 Replies
6. Programming
Some one please explain me what is Dynamic memory allocation and the use of malloc() function.How do we allocate memory dynamically and also the other way? (3 Replies)
Discussion started by: rash123
3 Replies
7. Programming
Hey Guys
I am trying to implement the malloc function for my OS class and I am having a little trouble with it. I would be really grateful if I could get some hints on this problem.
So I am using a doubly-linked list as my data structure and I have to allocate memory for it (duh...). The... (1 Reply)
Discussion started by: Gambit_b
1 Replies
8. UNIX for Dummies Questions & Answers
Do kmalloc and malloc allocate from same heap ? (3 Replies)
Discussion started by: dragonpoint
3 Replies
9. Programming
Which one is faster among malloc and new?
My understanding is that since new also has to call constructors after allocating memory it must be slower than malloc.
Am I correct? (1 Reply)
Discussion started by: rupeshkp728
1 Replies
10. UNIX for Dummies Questions & Answers
Good day! I'm a newbie in C. I'm trying to get an unlimited input from the user using malloc then printing the inputs after the user presses enter. My code works, but there's a warning that I don't know how to fix. Please help me. Thank you.
Here's my code:
#include <stdio.h>
#include... (6 Replies)
Discussion started by: eracav
6 Replies
LEARN ABOUT DEBIAN
physfs_allocator
PHYSFS_Allocator(3) physfs PHYSFS_Allocator(3)
NAME
PHYSFS_Allocator -
PhysicsFS allocation function pointers.
SYNOPSIS
#include <physfs.h>
Data Fields
int(* Init )(void)
void(* Deinit )(void)
void *(* Malloc )(PHYSFS_uint64)
void *(* Realloc )(void *, PHYSFS_uint64)
void(* Free )(void *)
Detailed Description
PhysicsFS allocation function pointers.
(This is for limited, hardcore use. If you don't immediately see a need for it, you can probably ignore this forever.)
You create one of these structures for use with PHYSFS_setAllocator. Allocators are assumed to be reentrant by the caller; please mutex
accordingly.
Allocations are always discussed in 64-bits, for future expansion...we're on the cusp of a 64-bit transition, and we'll probably be
allocating 6 gigabytes like it's nothing sooner or later, and I don't want to change this again at that point. If you're on a 32-bit
platform and have to downcast, it's okay to return NULL if the allocation is greater than 4 gigabytes, since you'd have to do so anyhow.
See also:
PHYSFS_setAllocator
Field Documentation
void(* PHYSFS_Allocator::Deinit)(void) Deinitialize your allocator. Can be NULL.
void(* PHYSFS_Allocator::Free)(void *) Free memory from Malloc or Realloc.
int(* PHYSFS_Allocator::Init)(void) Initialize. Can be NULL. Zero on failure.
void*(* PHYSFS_Allocator::Malloc)(PHYSFS_uint64) Allocate like malloc().
void*(* PHYSFS_Allocator::Realloc)(void *, PHYSFS_uint64) Reallocate like realloc().
Author
Generated automatically by Doxygen for physfs from the source code.
Version 2.0.2 Fri Feb 24 2012 PHYSFS_Allocator(3)