Re: lib-bsd socket close issues

On 05/04/2019 01:17, Chris Johns wrote: On 5/4/19 4:53 am, Matthew J Fletcher wrote: Hi Sebastian I used rtems_task_wake_after(). On Thu, 4 Apr 2019, 18:22 Sebastian Huber, mailto:sebastian.hu...@embedded-brains.de>> wrote: How do you wait. Is this a busy wait? - Matthew J Fle

Re: RTEMS scheduler bug ?

On 5/4/19 3:56 pm, Sebastian Huber wrote: > On 05/04/2019 06:52, Chris Johns wrote: >> On 5/4/19 3:36 pm, Sebastian Huber wrote: >>> However, who knows that this manual exists and reads it? >> Why not add a link or reference in the BSP's section in the user manual? > > From my point of view the CP

Re: RTEMS scheduler bug ?

On 05/04/2019 06:52, Chris Johns wrote: On 5/4/19 3:36 pm, Sebastian Huber wrote: However, who knows that this manual exists and reads it? Why not add a link or reference in the BSP's section in the user manual? From my point of view the CPU port documentation belongs to the user manual. In

Re: RTEMS scheduler bug ?

On 5/4/19 3:36 pm, Sebastian Huber wrote: > However, who knows that this manual exists and reads it? Why not add a link or reference in the BSP's section in the user manual? Thanks Chris ___ users mailing list users@rtems.org http://lists.rtems.org/mai

Re: RTEMS scheduler bug ?

On 04/04/2019 15:23, Joel Sherrill wrote: On Thu, Apr 4, 2019 at 7:28 AM Sebastian Huber > wrote: Hello, On 04/04/2019 14:09, Catalin Demergian wrote: > Hi Andrei, > thank you for the elaborated answer ! > > I checked my STM

Re: lib-bsd socket close issues

On 5/4/19 4:53 am, Matthew J Fletcher wrote: > Hi Sebastian > > I used rtems_task_wake_after(). > > > On Thu, 4 Apr 2019, 18:22 Sebastian Huber, > wrote: > > How do you wait. Is this a busy wait? > > - Matthew J Fletcher mailto:ami...@gma

Re: lib-bsd socket close issues

Hi Sebastian I used rtems_task_wake_after(). On Thu, 4 Apr 2019, 18:22 Sebastian Huber, < sebastian.hu...@embedded-brains.de> wrote: > How do you wait. Is this a busy wait? > > - Matthew J Fletcher schrieb: > > replying to myself. > > > > With a 1 second pause between socket() and close()

Re: lib-bsd socket close issues

How do you wait. Is this a busy wait? - Matthew J Fletcher schrieb: > replying to myself. > > With a 1 second pause between socket() and close() and 512 sockets it will > still ENOBUFS,.. without calculating it properly thats easily 10 minutes > since the first socket was allocated,. that mu

Re: lib-bsd socket close issues

replying to myself. With a 1 second pause between socket() and close() and 512 sockets it will still ENOBUFS,.. without calculating it properly thats easily 10 minutes since the first socket was allocated,. that must be enough time to start freeing the socket buffers internally. On Thu, 4 Apr 20

Re: RTEMS scheduler bug ?

> On 2019-April-04, at 7:23 AM, Joel Sherrill wrote: > > > > On Thu, Apr 4, 2019 at 7:28 AM Sebastian Huber > > wrote: > Hello, > > On 04/04/2019 14:09, Catalin Demergian wrote: > > Hi Andrei, > > thank you for the elaborated answer ! > > > > I ch

Re: RTEMS scheduler bug ?

What methods are available for altering an interrupt's priority in RTEMS? There's some mention of supporting up to 256 priorities, but no mention of how to adjust an interrupt's priority through the interrupt manager. It looks like I've got to use the interrupt controller's registers directly, an

lib-bsd socket close issues

Hi, I have noticed an issue with lib-bsd that the legacy stack does not have. If have a loop that does for (;;) { wait(100) // milliseconds socket() // allocate close() // free } then i can see the socket numbers allocated upwards, but eventually the get ENOBUFS from socket(),.. allocatin

Re: RTEMS scheduler bug ?

On Thu, Apr 4, 2019 at 7:28 AM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > Hello, > > On 04/04/2019 14:09, Catalin Demergian wrote: > > Hi Andrei, > > thank you for the elaborated answer ! > > > > I checked my STM32 Cube settings, I have 3 enabled interrupts and they > > all hav

Re: RTEMS scheduler bug ?

Hello, On 04/04/2019 14:09, Catalin Demergian wrote: Hi Andrei, thank you for the elaborated answer ! I checked my STM32 Cube settings, I have 3 enabled interrupts and they all have the preemption priority/sub priority set to zero ! it seems I ran into the same issue you had in 2015 :) I will

Re: RTEMS scheduler bug ?

Hi Andrei, thank you for the elaborated answer ! I checked my STM32 Cube settings, I have 3 enabled interrupts and they all have the preemption priority/sub priority set to zero ! it seems I ran into the same issue you had in 2015 :) I will take your advice - change the priorities, regenerate the