public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
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 22:01:01 +0000	[thread overview]
Message-ID: <ed5aea43050830150112ee6103@mail.gmail.com> (raw)
In-Reply-To: <17170.30144.755169.205802@berry.gelato.unsw.EDU.AU>

Ah, I understand now what you mean.  Sounds to me like the generic
module loader infrastructure needs to be changed to support the
IA64-usage.  On IA64, we want to have per-CPU variables remapped even
on UP, because it allows for more efficient and TLB-pinned addressing
(which is relied upon in some low-level code for correctness, IIRC).

  --david

On 8/30/05, Peter Chubb <peterc@gelato.unsw.edu.au> wrote:
> >>>>> "david" = david mosberger <dmosberger@gmail.com> writes:
> 
> david> The module-loader does its own UP special-casing.  For
> david> example, percpu_modcopy() is a dummy routine in the UP case,
> david> apparently because there is not supposed to be any per-CPU
> david> module data for the UP case.
> 
> Precisely.  All the other architectures redefine the DECLARE_PER_CPU()
> etc., to declare plain variables (i.e., not in a special section) for
> UP.  So the module loader doesn't have to do anything special for UP,
> because for UP a per-cpu variable is just the same as a normal
> variable.
> 
> This doesn't work for IA64, which maps per_cpu variables into a
> separate segment for both UP and SMP.
> 
> --
> Dr Peter Chubb  http://www.gelato.unsw.edu.au  peterc AT gelato.unsw.edu.au
> The technical we do immediately,  the political takes *forever*
> 


-- 
Mosberger Consulting LLC, voice/fax: 510-744-9372,
http://www.mosberger-consulting.com/
35706 Runckel Lane, Fremont, CA 94536

  parent reply	other threads:[~2005-08-30 22:01 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
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 [this message]
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=ed5aea43050830150112ee6103@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