All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: dipankar@in.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] New per-cpu patch v2.5.1
Date: Thu, 27 Dec 2001 17:50:33 +1100	[thread overview]
Message-ID: <20011227175033.13e1fcd0.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20011220174335.A10791@in.ibm.com>
In-Reply-To: <20011220174335.A10791@in.ibm.com>

On Thu, 20 Dec 2001 17:43:35 +0530
Dipankar Sarma <dipankar@in.ibm.com> wrote:

> Hi Rusty,
> 
> I appreciate the noble gesture of allowing NUMA people to
> locate the per-cpu areas in different places in memory ;-)
> 
> That said, memcpy of static per-cpu areas doesn't seem right.
> Why copy the same area to all the dynamically allocated per-cpu
> areas ?

Initialization.  Sure, we can't do it with the current macros...

> Also, shouldn't the size be &__per_cpu_end - &__per_cpu_start ?

Oops...  Yes.  (I wrote this just before my Xmas break, and didn't have time
to test it).

> And how do we use this with per-cpu data used right
> from smp boot, say apic_timer_irqs[] ?

No.  You can't have everthing (without going into the arch-specific code).

Cheers,
Rusty.
-- 
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2001-12-30  4:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-20 12:13 [PATCH] New per-cpu patch v2.5.1 Dipankar Sarma
2001-12-27  6:50 ` Rusty Russell [this message]
2002-01-13  5:52 ` Rusty Russell
  -- strict thread matches above, loose matches on Subject: below --
2001-12-20  6:15 Rusty Russell
2001-12-20  6:24 ` Robert Love
2001-12-26  0:39   ` Rusty Russell

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=20011227175033.13e1fcd0.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=dipankar@in.ibm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.