[RTEMS Project] #4033: Add rtems_interrupt_server_create() and rtems_interrupt_server_destroy()

[RTEMS trac]

#4033: Add rtems_interrupt_server_create() and rtems_interrupt_server_destroy()
-----------------------------+------------------------------
 Reporter:  Sebastian Huber  |       Owner:  Sebastian Huber
     Type:  enhancement      |      Status:  closed
 Priority:  normal           |   Milestone:  5.1
Component:  lib              |     Version:  5
 Severity:  normal           |  Resolution:  fixed
 Keywords:                   |  Blocked By:
 Blocking:                   |
-----------------------------+------------------------------
Changes (by Sebastian Huber <sebastian.huber@…>):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"5eb07731594fba04eedcbb72939abf3112a98bdb/rtems"
 5eb07731/rtems]:
 {{{
 #!CommitTicketReference repository="rtems"
 revision="5eb07731594fba04eedcbb72939abf3112a98bdb"
 rtems: Add rtems_interrupt_server_create()

 Add rtems_interrupt_server_destroy().

 Before this patch, the only way to create interrupt servers was
 rtems_interrupt_server_initialize(). This function creates the default
 interrupt server and in SMP configurations additional interrupt servers
 for the additional processors. The interrupt server is heavily used by
 libbsd. This includes the epoch based reclamation which performs time
 consuming resource and memory deallocation work. This does not work well
 with time critical services, for example an UART over SPI or I2C. One
 approach to address this problem is to allow the application to create
 custom interrupt servers with the right priority and task properties.
 The interrupt server API accounted for this, however, it was not
 implemented before this patch.

 Close #4033.
 }}}

--
Ticket URL: <http://devel.rtems.org/ticket/4033#comment:2>
RTEMS Project <http://www.rtems.org/>
RTEMS Project