From: david mosberger <dmosberger@gmail.com>
To: linux-ia64@vger.kernel.org
Subject: Re: ip_contrack module refuses to load...
Date: Tue, 30 Aug 2005 18:38:17 +0000 [thread overview]
Message-ID: <ed5aea4305083011384b38ad1a@mail.gmail.com> (raw)
In-Reply-To: <17170.30144.755169.205802@berry.gelato.unsw.EDU.AU>
On 8/30/05, Luck, Tony <tony.luck@intel.com> wrote:
> At first glance it looks like ia64 should not be treating the UP
> case differently from the SMP case. UP kernels place the per-cpu
> data up in the top 64K (PERCPU_PAGE_SIZE) of the virtual address
> space mapped by DTR[1], just like SMP kernels do ...
That's true.
> so all the
> space allocation, mapping, and relocation code should be the same
> for UP and SMP ... shouldn't they?
No, in the UP case, we can simply map the per-CPU section in the
kernel image whereas in the SMP case, each CPU needs its own copy of
the per-CPU section. To see this, look for per_cpu_init(): in the SMP
case, it copies the section, in the UP-case, it simply returns
__phys_per_cpu_start (a pointer into the per-CPU section).
--david
--
Mosberger Consulting LLC, voice/fax: 510-744-9372,
http://www.mosberger-consulting.com/
35706 Runckel Lane, Fremont, CA 94536
next prev parent reply other threads:[~2005-08-30 18:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-29 2:41 ip_contrack module refuses to load Peter Chubb
2005-08-29 4:09 ` Luck, Tony
2005-08-29 7:29 ` Peter Chubb
2005-08-30 1:35 ` Peter Chubb
2005-08-30 16:17 ` Luck, Tony
2005-08-30 18:38 ` david mosberger [this message]
2005-08-30 19:22 ` Luck, Tony
2005-08-30 19:29 ` david mosberger
2005-08-30 21:52 ` Peter Chubb
2005-08-30 22:01 ` david mosberger
2005-09-01 4:59 ` ip_contrack refuses to load if built UP as a module on IA64 Peter Chubb
2005-09-22 22:04 ` dann frazier
2005-12-19 21:07 ` Luck, Tony
2006-01-10 21:21 ` dann frazier
2006-01-22 19:31 ` dann frazier
2005-09-02 3:37 ` ip_contrack module refuses to load Herbert Poetzl
2005-09-02 3:45 ` Luck, Tony
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=ed5aea4305083011384b38ad1a@mail.gmail.com \
--to=dmosberger@gmail.com \
--cc=linux-ia64@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