mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Hai Xu" <xhai@CLEMSON.EDU>
To: <linux-kernel@vger.kernel.org>
Subject: Question about mm.h and mmzone.h
Date: Wed, 25 Jul 2001 12:30:27 -0400	[thread overview]
Message-ID: <000701c11527$1d4c44d0$3cac7f82@crb50> (raw)

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


             reply	other threads:[~2001-07-25 16:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-25 16:30 Hai Xu [this message]
2001-08-08 10:54 Nitin Dhingra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000701c11527$1d4c44d0$3cac7f82@crb50' \
    --to=xhai@clemson.edu \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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®