Re: RTEMS5 and file descriptors

2022-10-20 Thread Miroslaw Dach
Thank you Joel for all of the hints. I find the maximum number - 64 - of file descriptors somehow low when compared with Linux and RTEMS 4 (RTEMS 4 did not have the restriction with FD_SETSIZE). Anyhow, my application is EPICS base and most of the open file descriptors refer to the clients which

Re: RTEMS5 and file descriptors

2022-10-19 Thread Chris Johns
On 20/10/2022 4:03 am, Michael Davidsaver wrote: > On 10/17/22 22:50, Chris Johns wrote: >> On 18/10/2022 4:42 pm, Sebastian Huber wrote: >>> On 18/10/2022 06:15, Chris Johns wrote: On 18/10/2022 2:22 pm, Michael Davidsaver wrote: > On 10/17/22 16:20, Chris Johns wrote: >> 2. Look at

Re: RTEMS5 and file descriptors

2022-10-19 Thread Michael Davidsaver
On 10/17/22 22:50, Chris Johns wrote: On 18/10/2022 4:42 pm, Sebastian Huber wrote: On 18/10/2022 06:15, Chris Johns wrote: On 18/10/2022 2:22 pm, Michael Davidsaver wrote: On 10/17/22 16:20, Chris Johns wrote: 2. Look at kqueue, it is a better interface for this type of blocking Maybe not

Re: RTEMS5 and file descriptors

2022-10-17 Thread Chris Johns
On 18/10/2022 4:42 pm, Sebastian Huber wrote: > On 18/10/2022 06:15, Chris Johns wrote: >> On 18/10/2022 2:22 pm, Michael Davidsaver wrote: >>> On 10/17/22 16:20, Chris Johns wrote: 2. Look at kqueue, it is a better interface for this type of blocking >>> Maybe not relevant in Miroslaw's

Re: RTEMS5 and file descriptors

2022-10-17 Thread Sebastian Huber
On 18/10/2022 06:15, Chris Johns wrote: On 18/10/2022 2:22 pm, Michael Davidsaver wrote: On 10/17/22 16:20, Chris Johns wrote: 2. Look at kqueue, it is a better interface for this type of blocking Maybe not relevant in Miroslaw's application, but I've found that the RTEMS kqueue

Re: RTEMS5 and file descriptors

2022-10-17 Thread Chris Johns
On 18/10/2022 2:22 pm, Michael Davidsaver wrote: > On 10/17/22 16:20, Chris Johns wrote: >> 2. Look at kqueue, it is a better interface for this type of blocking > > Maybe not relevant in Miroslaw's application, but I've found > that the RTEMS kqueue implementation doesn't notify when a > TCP

Re: RTEMS5 and file descriptors

2022-10-17 Thread Michael Davidsaver
On 10/17/22 16:20, Chris Johns wrote: 2. Look at kqueue, it is a better interface for this type of blocking Maybe not relevant in Miroslaw's application, but I've found that the RTEMS kqueue implementation doesn't notify when a TCP connection is closed by reset. I think this is a lack of

Re: RTEMS5 and file descriptors

2022-10-17 Thread Chris Johns
On 18/10/2022 9:19 am, Miroslaw Dach wrote: >>AFAIK you'd have to patch the header in the C Library when building the tools > using the RSB to have a possible clean solution. Editing the installed header > would be uncool. > I see , I thought that it is somehow simpler thing. >>How many

Re: RTEMS5 and file descriptors

2022-10-17 Thread Miroslaw Dach
Hi Joel, Thank you for your quick answer. >AFAIK you'd have to patch the header in the C Library when building the tools using the RSB to have a possible clean solution. Editing the installed header would be uncool. I see , I thought that it is somehow simpler thing. >How many descriptors do you

Re: RTEMS5 and file descriptors

2022-10-17 Thread Joel Sherrill
On Mon, Oct 17, 2022, 12:23 PM Miroslaw Dach wrote: > Hello, > > I have followed the instruction to change the limit of File Descriptors > higher than 64: > > https://docs.rtems.org/branches/master/user/migration/v4_11-to-v5.html > chapter 13.1.3. File Descriptors > > Is it required to rebuild

RTEMS5 and file descriptors

2022-10-17 Thread Miroslaw Dach
Hello, I have followed the instruction to change the limit of File Descriptors higher than 64: https://docs.rtems.org/branches/master/user/migration/v4_11-to-v5.html chapter 13.1.3. File Descriptors Is it required to rebuild the RTEMS5 kernel with the macro FD_SETSIZE set to the higher value