All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Tejun Heo <tj@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Al Viro <viro@ZenIV.linux.org.uk>, Mike Travis <travis@sgi.com>,
	Christoph Lameter <cl@linux-foundation.org>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] unbreak alpha percpu
Date: Fri, 10 Apr 2009 21:34:44 +0200	[thread overview]
Message-ID: <20090410193444.GA18039@elte.hu> (raw)
In-Reply-To: <49DF97D0.9090506@kernel.org>


* Tejun Heo <tj@kernel.org> wrote:

> Long term, I think what Ivan proposed with a bit of addition so 
> that combination of DECLARE_PER_CPU() and static DEFINE_PER_CPU() 
> triggers compile error but I think it's better to do it when 
> converting non-x86 archs to dynamic percpu allocator which is 
> scheduled for the next merge window.  For the time being, how 
> about just moving the generic percpu_*() accessors to 
> linux/percpu.h?  asm-generic/percpu.h is meant to carry generic 
> stuff for low level stuff - declarations, definitions and pointer 
> offset calculation and so on but not for generic interface.
> 
> I currently can't build or test stuff so the patch is not tested 
> at all.  Ingo, can you please test whether this would work?

Yes - but i'm somewhat confused - i frequently cross-built Alpha and 
other architectures as well.

So exactly what problem do we have here - has some devel tree grown 
new use of these APIs in generic code, without waiting for all 
arches to be properly converted?

(sounds of rummaging around)

Oh drat:

| commit 4e69489a0ac11a9b62a25923975bfc370a30eae5
| Author: Eric Dumazet <dada1@cosmosbay.com>
| Date:   Sat Apr 4 16:41:09 2009 -0700
|
|     socket: use percpu_add() while updating sockets_in_use

Now i understand the rush ...

Yes, moving the APIs to the generic header should properly expose 
the wrapped default implementations. I'll test your patch in a 
minute.

	Ingo

  reply	other threads:[~2009-04-10 19:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-10 15:12 [PATCH] unbreak alpha percpu Al Viro
2009-04-10 15:47 ` Al Viro
2009-04-10 16:21   ` Linus Torvalds
2009-04-10 16:50     ` Al Viro
2009-04-10 17:05       ` Al Viro
2009-04-10 17:14         ` Al Viro
2009-04-10 18:05           ` Ivan Kokshaysky
2009-04-10 18:20             ` Linus Torvalds
2009-04-10 18:43               ` Tejun Heo
2009-04-10 19:02                 ` Tejun Heo
2009-04-10 19:34                   ` Ingo Molnar [this message]
2009-04-10 19:40                     ` [GIT PULL] percpu + mutex fixes Ingo Molnar
2009-04-16 10:21                       ` Al Viro
2009-04-14  7:45     ` [PATCH] unbreak alpha percpu Martin Schwidefsky
2009-04-14  9:01       ` Tejun Heo

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=20090410193444.GA18039@elte.hu \
    --to=mingo@elte.hu \
    --cc=cl@linux-foundation.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=travis@sgi.com \
    --cc=viro@ZenIV.linux.org.uk \
    /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.