Re: CONFIG_NFILE_DESCRIPTORS considerations and limitations
Just saw that I had responded to Gregs mail individually. Sending to the list just to finish the topic.. Best, Florian On 24/01/2020 22:07, Florian Wehmeyer wrote: Hi Greg, thanks for the ultra-fast reply!! Turns out the problem of system panic after increasing CONFIG_NFILE_DESCRIPTORS was due to inconsistent compile, some of the file descriptor structures might not have been compiled with correct sizes. When running a make clean before compiling everything works great. I guess a "make clean" should be default practice after changing anything in the config. CONFIG_STDIO_BUFFER_SIZE for those devices is already 0 because of CONFIG_STDIO_DISABLE_BUFFERING=y Best, Florian On 24/01/2020 18:24, Gregory Nutt wrote: 1) am I doing bad practice, opening that much file descriptors per task? if yes, I could open and close them on each access, which is actually each 100ms, if that would be less overhead (guess not). No, it is perfectly fine to change the number of descriptors, provided that you have at least 3. 2)Of course I tried to set CONFIG_NFILE_DESCRIPTORS=8, but when I do that, the system jumps into arch/arm/src/armv6-m/up_assert.c :_up_assert(), before even finishing nx_start(). Is there anything else that must be considered when increasing the CONFIG_NFILE_DESCRIPTORS? No, other than it will greatly increase memory usage. That is a big deal on that platform. Check CONFIG_STDIO_BUFFER_SIZE, the increased memory usage will go into (1) file descriptor structures, and (2) buffers for C-buffered I/O. You can set CONFIG_STDIO_BUFFER_SIZE as low as zero, but then you will have no buffering that that will affect realtime preformance. Greg -- Florian Wehmeyer TFW Tech Solutions
Podling Nuttx Report Reminder - February 2020
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 19 February 2020, 10:30 am PDT. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, February 05). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Candidate names should not be made public before people are actually elected, so please do not include the names of potential committers or PPMC members in your report. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. * How does the podling rate their own maturity. This should be appended to the Incubator Wiki page at: https://cwiki.apache.org/confluence/display/INCUBATOR/February2020 Note: This is manually populated. You may need to wait a little before this page is created from a template. Note: The format of the report has changed to use markdown. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
