<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Supported memory pool size on Thingy91</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/60980/supported-memory-pool-size-on-thingy91</link><description>Hello, 
 I am working on a BLE application for the Thingy91 which needs a lot of dynamic memory. In the Zephyr specification values of up to 16kB are supported. I tried to increase the pool size to 32kB and this seems to work fine. 
 Hence my question</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 05 May 2020 06:19:26 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/60980/supported-memory-pool-size-on-thingy91" /><item><title>RE: Supported memory pool size on Thingy91</title><link>https://devzone.nordicsemi.com/thread/248048?ContentTypeID=1</link><pubDate>Tue, 05 May 2020 06:19:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f04112b4-ed04-4515-ac5c-ac4ee68837fc</guid><dc:creator>Nils Ruf</dc:creator><description>&lt;p&gt;Hi Didrik,&lt;/p&gt;
&lt;p&gt;thank you very much for that explanation. You helped me a lot.&lt;/p&gt;
&lt;p&gt;Kind regards&lt;br /&gt;Nils&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Supported memory pool size on Thingy91</title><link>https://devzone.nordicsemi.com/thread/247936?ContentTypeID=1</link><pubDate>Mon, 04 May 2020 14:39:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:443bc105-6f6f-426c-a493-5e24c7cc3152</guid><dc:creator>Didrik Rokhaug</dc:creator><description>&lt;p&gt;Hi.&lt;/p&gt;
&lt;p&gt;According to one of our developers, you can safely disregard the limits stated in the documentation.&lt;/p&gt;
&lt;p&gt;But, there are some details regarding Zephyr&amp;#39;s current heap allocation algorithm that is worth noting:&lt;/p&gt;
&lt;p&gt;&amp;quot;Heap looks for chunk by dividing the big block into 4 subblocks. it goes down until it matches with the min block size from the configuration. In our case for example we have heap 512 minblock 32. Now we could increase heap to 1024 but that means the smallest chunk would be 64 bytes. It cannot divide yt as 64/4 is 16 and smaller then 32. So in the end we can allocate the same amount of chunks&amp;quot;&lt;/p&gt;
&lt;p&gt;This means that &amp;quot;a 32k heap would double the size available, but not increase the number of possible minimal&amp;nbsp;blocks, whereas 64k would quadruple both space and possible minimal&amp;nbsp;blocks&amp;quot;.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Didrik&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>