From: Tejun Heo <tj@kernel.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: David Miller <davem@davemloft.net>,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] percpu misaligned allocation
Date: Fri, 19 Mar 2010 01:51:32 +0000 [thread overview]
Message-ID: <4BA2D8A4.2080409@kernel.org> (raw)
In-Reply-To: <20100319013119.GB22095@nowhere>
Hello,
On 03/19/2010 10:31 AM, Frederic Weisbecker wrote:
> 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?
Sure, I just wanted to verify the cause of the problem.
> 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.
If you can't make it a proper type, __alignof__(unsigned long long)
would be better.
> 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.
I hope those macros align properly according to types.
Thanks.
--
tejun
WARNING: multiple messages have this Message-ID (diff)
From: Tejun Heo <tj@kernel.org>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: David Miller <davem@davemloft.net>,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] percpu misaligned allocation
Date: Fri, 19 Mar 2010 10:51:32 +0900 [thread overview]
Message-ID: <4BA2D8A4.2080409@kernel.org> (raw)
In-Reply-To: <20100319013119.GB22095@nowhere>
Hello,
On 03/19/2010 10:31 AM, Frederic Weisbecker wrote:
> 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?
Sure, I just wanted to verify the cause of the problem.
> 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.
If you can't make it a proper type, __alignof__(unsigned long long)
would be better.
> 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.
I hope those macros align properly according to types.
Thanks.
--
tejun
next prev parent reply other threads:[~2010-03-19 1:51 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-18 4:49 [BUG] percpu misaligned allocation Frederic Weisbecker
2010-03-18 4:49 ` Frederic Weisbecker
2010-03-18 6:26 ` David Miller
2010-03-18 6:26 ` David Miller
2010-03-18 6:28 ` David Miller
2010-03-18 6:28 ` David Miller
2010-03-18 6:36 ` Li Zefan
2010-03-18 6:36 ` Li Zefan
2010-03-18 6:39 ` Li Zefan
2010-03-18 6:39 ` Li Zefan
2010-03-18 16:56 ` Frederic Weisbecker
2010-03-18 16:56 ` Frederic Weisbecker
2010-03-18 9:30 ` Tejun Heo
2010-03-18 9:30 ` Tejun Heo
2010-03-18 19:50 ` Frederic Weisbecker
2010-03-18 19:50 ` Frederic Weisbecker
2010-03-19 0:54 ` David Miller
2010-03-19 0:54 ` David Miller
2010-03-19 1:31 ` Frederic Weisbecker
2010-03-19 1:31 ` Frederic Weisbecker
2010-03-19 1:51 ` Tejun Heo [this message]
2010-03-19 1:51 ` Tejun Heo
2010-03-19 1:57 ` David Miller
2010-03-19 1:57 ` David Miller
2010-03-19 2:18 ` Tejun Heo
2010-03-19 2:18 ` Tejun Heo
2010-03-19 2:30 ` Frederic Weisbecker
2010-03-19 2:30 ` Frederic Weisbecker
2010-03-19 3:02 ` David Miller
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=4BA2D8A4.2080409@kernel.org \
--to=tj@kernel.org \
--cc=davem@davemloft.net \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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.