Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001116
--- Comment #44 from Sergei Gavrikov <[email protected]> 2011-01-31 18:16:42 GMT --- (In reply to comment #43) > (In reply to comment #42) > > (In reply to comment #34) > > > > > > I am kind of undecided. Somebody else's opinion is welcome. > > > ^^^^^^^^ That would be fine. John, if > > > you read, what is your opinion? > > > > Sergei, is this about whether to place var_data[] in peripheral > > memory or to keep it in main memory? Is there something different > > about this array relative to those you are definitely moving to > > peripheral memory? > > John, > > The ones moved to peripheral memory are: memp_memory[] and ram_heap[] > i.e. arrays from which lwip allocates memory for pbufs, etc. It is > what would typically peripheral (hardware) do. > > var_data[] on the other hand contains thread related data (not > buffers). > > At the beginning I wanted to save as much as possible, but later as I > had gained some insight I have reconsidered my view. > > Other difference is that var_data[] is used in sequential mode which > is not very likely used on devices with low memory. > > Please refer to comment #36 and comment #37 for our further > conversation with Sergei. > > Thanks for your consideration > Ilija I'm sorry, I was AFK. John, if you have doubts about that voluntary reject those varibales from peripherial room (src/ecos/sys_arch.c: stack_data[] and var_data[]), let us know, please, I pend a commit. We discussed that a bit with Ilija and decided do not touch sys_arch.c. Sergei -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
