timerfd can be fairly easily replaced with a socketpair, where one
socket is used in the poll/select and the other is used to signal
activation.  To wake up the poll/select, write a character into the
signal socket.  You will need to be sure to read the characters out of
the select socket to make sure you don't get a full buffer and
back-pressure.

-Ted

On Thu, Sep 6, 2018 at 7:26 AM,  <n...@gmx.es> wrote:
>
> Hi,
>
> I am trying to port a project which was implemented using qpid-proton-cpp 
> from a fairly recent Fedora linux kernel to an older RHEL linux 2.6.
>
> The older kernel is required because the end user unfortunately only runs the 
> older linux kernel, and due to company policy they cannot upgrade in the near 
> future.
>
> Unfortunately when we try to build on linux kernel 2.6 there are dependency 
> issues which relate to the older kernel not including support for timerfd 
> which is used in qpid-proton-proactor.
>
> We did also encounter some other build issues with some of the cpp templates 
> in proton-cpp due to bugs in the older GNU compiler version which we fixed 
> using workarounds, but getting the proactor to work on the older kernel looks 
> like it will be less than trivial without timerfd.
>
> I do see what appears to be an older implementation for IO etc named reactor 
> as opposed to proactor in the proton c implementations, but unfortunately the 
> cpp container implementation which we are using does not seem to have an 
> implementation using reactor instead of proactor?
>
> Is there any way around this - is it possible to use container without having 
> timerfd support in the kernel?
>
> Performance isn't important for us in this so a simple socket read loop would 
> be fine - just I am not sure how to shoehorn that into what we have already 
> implemented using container...?
>
> Thanks
> N
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Reply via email to