* Question about mm.h and mmzone.h
@ 2001-07-25 16:30 Hai Xu
0 siblings, 0 replies; 2+ messages in thread
From: Hai Xu @ 2001-07-25 16:30 UTC (permalink / raw)
To: linux-kernel
Dear all,
What I am using is RH7.1+Linux Kernel 2.4.4.
When I compile my code under the 2.4.4 Linux Kernel, I will meet error as
follows:
In file included from /usr/src/linux/include/linux/slab.h:14,
from /usr/src/linux/include/linux/malloc.h:4,
from ../../../include/builtins++.h:42,
from example.cpp:12:
/usr/src/linux/include/linux/mm.h:461: conflicting types for `struct zone_t'
/usr/src/linux/include/linux/mmzone.h:61: previous declaration as `typedef
struct zone_struct zone_t'
In file included from /usr/rtlinux-3.1/include/rtl_sync.h:47,
from /usr/rtlinux-3.1/include/rtl_spinlock.h:13,
from /usr/rtlinux-3.1/include/rtl_time.h:46,
from example.cpp:20:
/usr/rtlinux-3.1/include/rtl_tracer.h:79: confused by earlier errors,
bailing out
make: *** [_example.o] Error 1
Any idea about it?
I have another question about the stucture -- page in the mm.h. What is
function of void *virtual in this struct? I can not understand this
definition.
typedef struct page {
struct list_head list;
struct address_space *mapping;
unsigned long index;
struct page *next_hash;
atomic_t count;
unsigned long flags; /* atomic flags, some possibly updated asynchronously
*/
struct list_head lru;
unsigned long age;
wait_queue_head_t wait;
struct page **pprev_hash;
struct buffer_head * buffers;
void *virtual; /* non-NULL if kmapped */
struct zone_struct *zone;
} mem_map_t;
thanks in advance
Hai Xu
^ permalink raw reply [flat|nested] 2+ messages in thread
* RE: Question about mm.h and mmzone.h
@ 2001-08-08 10:54 Nitin Dhingra
0 siblings, 0 replies; 2+ messages in thread
From: Nitin Dhingra @ 2001-08-08 10:54 UTC (permalink / raw)
To: 'Hai Xu', linux-kernel
The void *virtual entry is used in the page structure
to provide its virtual address of that page
-----Original Message-----
From: Hai Xu [mailto:xhai@CLEMSON.EDU]
Sent: Wednesday, July 25, 2001 9:30 AM
To: linux-kernel@vger.kernel.org
Subject: Question about mm.h and mmzone.h
Dear all,
What I am using is RH7.1+Linux Kernel 2.4.4.
When I compile my code under the 2.4.4 Linux Kernel, I will meet error as
follows:
In file included from /usr/src/linux/include/linux/slab.h:14,
from /usr/src/linux/include/linux/malloc.h:4,
from ../../../include/builtins++.h:42,
from example.cpp:12:
/usr/src/linux/include/linux/mm.h:461: conflicting types for `struct zone_t'
/usr/src/linux/include/linux/mmzone.h:61: previous declaration as `typedef
struct zone_struct zone_t'
In file included from /usr/rtlinux-3.1/include/rtl_sync.h:47,
from /usr/rtlinux-3.1/include/rtl_spinlock.h:13,
from /usr/rtlinux-3.1/include/rtl_time.h:46,
from example.cpp:20:
/usr/rtlinux-3.1/include/rtl_tracer.h:79: confused by earlier errors,
bailing out
make: *** [_example.o] Error 1
Any idea about it?
I have another question about the stucture -- page in the mm.h. What is
function of void *virtual in this struct? I can not understand this
definition.
typedef struct page {
struct list_head list;
struct address_space *mapping;
unsigned long index;
struct page *next_hash;
atomic_t count;
unsigned long flags; /* atomic flags, some possibly updated asynchronously
*/
struct list_head lru;
unsigned long age;
wait_queue_head_t wait;
struct page **pprev_hash;
struct buffer_head * buffers;
void *virtual; /* non-NULL if kmapped */
struct zone_struct *zone;
} mem_map_t;
thanks in advance
Hai Xu
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-08-08 10:54 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-07-25 16:30 Question about mm.h and mmzone.h Hai Xu
2001-08-08 10:54 Nitin Dhingra
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®