public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: ying.huang@intel.com, linux-arch@vger.kernel.org
Subject: Re: + separate-atomic_t-declaration-from-asm-atomich-into-asm-atomic_defh.patch added to -mm tree
Date: Fri, 29 Aug 2008 17:19:36 -0700	[thread overview]
Message-ID: <20080829171936.f5f8b53d.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080829233416.GC1239@parisc-linux.org>

On Fri, 29 Aug 2008 17:34:16 -0600
Matthew Wilcox <matthew@wil.cx> wrote:

> 
> I see you're fixing up the original patch without commenting on this at
> all.

Sob.  I'm just slogging away trying to get my tree to compile.

One more build error and I drop it all.

> On Fri, Aug 22, 2008 at 03:36:25PM -0600, Matthew Wilcox wrote:
> > On Fri, Aug 22, 2008 at 01:56:38PM -0700, akpm@linux-foundation.org wrote:
> > > Subject: Separate atomic_t declaration from asm/atomic.h into asm/atomic_def.h
> > > From: Huang Ying <ying.huang@intel.com>
> > > 
> > > asm/atomic.h contains both declaration and implementation of atomic_t.  So
> > > there are some implementation related files included in asm/atomic.h.  And
> > > atomic_t is a typedef.  Combination of above makes it impossible to use
> > > atomic_t in files included by atomic.h.  Such as atomic_t can not be used
> > > in linux/kernel.h on i386, because it is included by asm/atomic.h.
> > > 
> > > It is reasonable to separate declaration from implementation.  So a new
> > > file atomic_def.h is added for every architecture to accommodate the
> > > declaration of atomic_t.
> > 
> > Seems to me like all architectures could use:
> > 
> > +++ include/linux/atomic_type.h
> > +typedef struct { volatile int counter; } atomic_t;
> > +#ifdef CONFIG_64BIT
> > +typedef struct { volatile long counter; } atomic64_t;
> > +#endif
> > 
> > S390 has an __aligned__((4)) on theirs -- is this really necessary?
> > Doesn't s390 align ints to 4 bytes automatically?  If it doesn't, it
> > shouldn't be harmful to add it to other architectures (iirc m68k only
> > requires 2-byte alignment for ints ... hmm, wonder if their atomic_t is
> > really atomic if, say, it cross a page boundary ...)
> > 

Sounds right to me.

  reply	other threads:[~2008-08-30  0:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-22 20:56 + separate-atomic_t-declaration-from-asm-atomich-into-asm-atomic_defh.patch added to -mm tree akpm
2008-08-22 20:56 ` akpm
2008-08-22 21:36 ` Matthew Wilcox
2008-08-29 23:34   ` Matthew Wilcox
2008-08-30  0:19     ` Andrew Morton [this message]
2008-08-30 21:56   ` Roman Zippel
2008-09-01  9:21   ` Christian Borntraeger

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=20080829171936.f5f8b53d.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=ying.huang@intel.com \
    /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