The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: tj@kernel.org, sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] percpu misaligned allocation
Date: Fri, 19 Mar 2010 02:31:22 +0100	[thread overview]
Message-ID: <20100319013119.GB22095@nowhere> (raw)
In-Reply-To: <20100318.175413.183069013.davem@davemloft.net>

On Thu, Mar 18, 2010 at 05:54:13PM -0700, David Miller wrote:
> From: Tejun Heo <tj@kernel.org>
> Date: Thu, 18 Mar 2010 18:30:34 +0900
> 
> >  
> >  	if (!total_profile_count) {
> > -		buf = (char *)alloc_percpu(perf_trace_t);
> > +		buf = (char *)__alloc_percpu(sizeof(perf_trace_t),
> > +					     __alignof__(unsigned long));
> >  		if (!buf)
> >  			goto fail_buf;
> 
> Why not make perf_trace_t have the proper alignment?


So, making perf_trace_t as align(8) would do the trick?
I lack the knowledge about alignment layout for archs that
need aligned accesses.
At a first glance, what I would except is that every buffer
has a base address aligned, no?


> 
> That's better than patching around it like this.
> 
> Defining it as an array of char[]'s is just asking
> for lots of trouble.


Yeah but we need a generic type. This is because
our buffer can be of any random type to match all
the trace event layouts we have, all of them being
generated by macros.


  reply	other threads:[~2010-03-19  1:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18  4:49 [BUG] percpu misaligned allocation Frederic Weisbecker
2010-03-18  6:26 ` David Miller
2010-03-18  6:28   ` David Miller
2010-03-18  6:36     ` Li Zefan
2010-03-18  6:39   ` Li Zefan
2010-03-18 16:56     ` Frederic Weisbecker
2010-03-18  9:30 ` Tejun Heo
2010-03-18 19:50   ` Frederic Weisbecker
2010-03-19  0:54   ` David Miller
2010-03-19  1:31     ` Frederic Weisbecker [this message]
2010-03-19  1:51       ` Tejun Heo
2010-03-19  1:57       ` David Miller
2010-03-19  2:18         ` Tejun Heo
2010-03-19  2:30           ` Frederic Weisbecker
2010-03-19  3:02           ` David Miller
2010-03-19 15:48             ` Richard Kennedy
2010-03-24 20:54 ` Maciej Rutecki

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=20100319013119.GB22095@nowhere \
    --to=fweisbec@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=tj@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