public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Houston <jim.houston@ccur.com>
To: george anzinger <george@mvista.com>
Cc: jim.houston@attbi.com, linux-kernel@vger.kernel.org,
	high-res-timers-discourse@lists.sourceforge.net
Subject: Re: [PATCH] alternate Posix timer patch
Date: Wed, 23 Oct 2002 15:48:26 -0400	[thread overview]
Message-ID: <3DB6FD0A.74BB3AD0@ccur.com> (raw)
In-Reply-To: 3DB6ED10.A81B0429@mvista.com

george anzinger wrote:
> 
> Jim Houston wrote:
> I have also looked at the timer index stuff and made a few
> changes.  If it get it working today, I will include it
> also.  My changes mostly revolved around not caring about
> reusing a timer id.  Would you care to comment on why you
> think reuse is bad?
> 
> With out this feature the code is much simpler and does not
> keep around dead trees.
> 
> -g

Hi George,

I assume the rationale is that not reusing the same id immediately helps
catch errors in user code.  Since the id space is global, there
is more chance that one process may be manipulating another processes
timer.  Reusing the same id makes this sort of problem harder to 
catch.

The main reason I changed this in my patch is to avoid the CONFIG
limit on the number of timers.  Since I don't have the fixed array,
I need a way to safely translate a user-space id into a kernel pointer.

Jim Houston Concurrent Computer Corp.

  reply	other threads:[~2002-10-23 19:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-23  8:38 [PATCH] alternate Posix timer patch Jim Houston
2002-10-23 18:40 ` george anzinger
2002-10-23 19:48   ` Jim Houston [this message]
2002-10-23 22:18     ` george anzinger
     [not found]     ` <200210232112.RAA09961@mc.com>
2002-10-23 22:36       ` george anzinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3DB6FD0A.74BB3AD0@ccur.com \
    --to=jim.houston@ccur.com \
    --cc=george@mvista.com \
    --cc=high-res-timers-discourse@lists.sourceforge.net \
    --cc=jim.houston@attbi.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox