On Tue, 27 Aug 2019, Frederic Weisbecker wrote:
> On Tue, Aug 27, 2019 at 08:08:06AM +0200, Thomas Gleixner wrote:
> > On Tue, 27 Aug 2019, Frederic Weisbecker wrote:
> >
> > > On Wed, Aug 21, 2019 at 09:09:25PM +0200, Thomas Gleixner wrote:
> > > > /**
> > > > @@ -92,14 +130,10 @@ struct posix_c
On Tue, Aug 27, 2019 at 08:08:06AM +0200, Thomas Gleixner wrote:
> On Tue, 27 Aug 2019, Frederic Weisbecker wrote:
>
> > On Wed, Aug 21, 2019 at 09:09:25PM +0200, Thomas Gleixner wrote:
> > > /**
> > > @@ -92,14 +130,10 @@ struct posix_cputimers {
> > >
> > > static inline void posix_cputimers
On Tue, 27 Aug 2019, Frederic Weisbecker wrote:
> On Wed, Aug 21, 2019 at 09:09:25PM +0200, Thomas Gleixner wrote:
> > /**
> > @@ -92,14 +130,10 @@ struct posix_cputimers {
> >
> > static inline void posix_cputimers_init(struct posix_cputimers *pct)
> > {
> > - pct->timers_active = 0;
> > -
On Wed, Aug 21, 2019 at 09:09:25PM +0200, Thomas Gleixner wrote:
> /**
> @@ -92,14 +130,10 @@ struct posix_cputimers {
>
> static inline void posix_cputimers_init(struct posix_cputimers *pct)
> {
> - pct->timers_active = 0;
> - pct->expiry_active = 0;
No more need to initialize these?
Using a linear O(N) search for timer insertion affects execution time and
D-cache footprint badly with a larger number of timers.
Switch the storage to a timerqueue which is already used for hrtimers and
alarmtimers. It does not affect the size of struct k_itimer as it.alarm is
still larger.
The
5 matches
Mail list logo