From: Alexey Skidanov <alexey.skidanov@intel.com>
To: Stephen Bates <sbates@raithlin.com>,
"danielmentz@google.com" <danielmentz@google.com>,
"mathieu.desnoyers@efficios.co" <mathieu.desnoyers@efficios.co>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Laura Abbott <labbott@redhat.com>
Subject: Re: lib/genalloc
Date: Thu, 1 Nov 2018 19:08:50 +0200 [thread overview]
Message-ID: <d127f28f-71fe-c175-c0e4-a368ff1d01a1@intel.com> (raw)
In-Reply-To: <4DECD467-AD45-419D-8F0F-1456863274FD@raithlin.com>
On 11/1/18 18:48, Stephen Bates wrote:
>> I use gen_pool_first_fit_align() as pool allocation algorithm allocating
>> buffers with requested alignment. But if a chunk base address is not
>> aligned to the requested alignment(from some reason), the returned
>> address is not aligned too.
>
> Alexey
>
> Can you try using gen_pool_first_fit_order_align()? Will that give you the alignment you need?
>
> Stephen
>
>
I think it will not help me. Let's assume that the chunk base address is
0x2F400000 and I want to allocate 16MB aligned buffer. I get back the
0x2F400000. I think it happens because of this string in the
gen_pool_alloc_algo():
addr = chunk->start_addr + ((unsigned long)start_bit << order);
and the gen_pool_first_fit_align() implementation that doesn't take into
account the "incorrect" chunk base alignment.
It might be easily fixed, by rounding the start address up (0x2F400000
-> 0x30000000) and start looking from this, aligned, address.
Thanks,
Alexey
next prev parent reply other threads:[~2018-11-01 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 16:43 lib/genalloc Alexey Skidanov
2018-11-01 16:48 ` lib/genalloc Stephen Bates
2018-11-01 17:08 ` Alexey Skidanov [this message]
2018-11-02 19:17 ` lib/genalloc Daniel Mentz
2018-11-02 20:56 ` lib/genalloc Alexey Skidanov
2018-11-02 21:16 ` lib/genalloc Daniel Mentz
2018-11-02 22:18 ` lib/genalloc Alexey Skidanov
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=d127f28f-71fe-c175-c0e4-a368ff1d01a1@intel.com \
--to=alexey.skidanov@intel.com \
--cc=danielmentz@google.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.co \
--cc=sbates@raithlin.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
all inboxes | Powered by JetHome®