Cool ... looking forward to it. > Am 27.01.2017 um 16:32 schrieb Kirils Mensikovs <[email protected]>: > > Thanks. I already start to work on it. Hope to get positive results over the > weekend. > >> On 26 January 2017 at 16:39, 'Norman Maurer' via Netty discussions >> <[email protected]> wrote: >> I see… >> >> yes its the right place to start (and also a few others). At some point I >> wanted to do something similar but could not prove any advantage here. That >> said I would love to review a PR :) >> >> Here is my old code which may gives you some good hints: >> >> https://github.com/netty/netty/pull/4726/ >> >> >>> On 26 Jan 2017, at 15:30, Kirils Mensikovs <[email protected]> wrote: >>> >>> Apache Arrow (http://arrow.apache.org/) uses netty buffers. All contiguous >>> memory buffers are aligned at 64-byte boundaries and padded to a multiple >>> of 64 bytes. Padding to a multiple of 64 bytes allows using SIMD >>> instructions consistently in loops without additional conditional check. >>> >>> Is PoolArena.normalizeCapazity(int capacity) is right place to start with? >>> >>> -Thanks >>> >>> >>> >>>> On Wednesday, January 25, 2017 at 8:19:26 PM UTC+2, Norman Maurer wrote: >>>> Why you need this ? >>>> >>>> There is currently not way to influence the alignment manual >>>> >>>> Am Dienstag, 24. Januar 2017 17:19:53 UTC+1 schrieb Kiril Menshikov: >>>>> >>>>> Hey, >>>>> >>>>> How can use PooledByteBufAllocator to allocate 64-byte align memory. >>>>> >>>>> Is it possible to know during memory request what memory address will be >>>>> 64-byte aligned: >>>>> >>>>> allocator.directBuffer(512, Integer.MAX_VALUE); >>>>> >>>>> Do you have recommendations how to do it? >>>>> >>>>> At the moment I can verify memorAddress and compute padding if necessary. >>>>> But in this case I need to modify size as well (size+padding). >>>>> >>>>> Thanks, >>>>> -Kiril >>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Netty discussions" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/netty/0e6f759f-4b8d-493b-8397-f67faa933cfb%40googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Netty discussions" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/netty/EwULtAWMYfI/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/netty/527EF78F-D3DC-4A87-92BE-57D8DB797B69%40googlemail.com. >> >> For more options, visit https://groups.google.com/d/optout. > > > > -- > Thanks, > -Kiril > Phone +37126409291 > Riga, Latvia > Skype perimetr122 > -- > You received this message because you are subscribed to the Google Groups > "Netty discussions" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/netty/CABgfpaoKa1zZ6h3w9nE8NubgfyutH7A5iHzJ1X9_XBFEiVJ0jQ%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout.
-- You received this message because you are subscribed to the Google Groups "Netty discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/netty/C7CDD36D-1CA8-4E0F-9AE2-2D9AD53D8EFD%40googlemail.com. For more options, visit https://groups.google.com/d/optout.
