From: george anzinger <george@mvista.com>
To: mbs <mbs@mc.com>
Cc: jim.houston@ccur.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] alternate Posix timer patch
Date: Wed, 23 Oct 2002 15:36:14 -0700 [thread overview]
Message-ID: <3DB7245E.B68D1FF4@mvista.com> (raw)
In-Reply-To: 200210232112.RAA09961@mc.com
mbs wrote:
>
> the way I handled this was that the timerid was the (kernel space) address of
> the dynamically allocated timer structure. this provides a fairly low
> likelyhood of duplicate timerid's value....
Yes, but this is a VERY messy pointer which must be verified
to not cause a kernel fault before it can even be
dereferenced... nuff said.
-g
by the way, the address mbs@mc.com fails. Maybe you could
use something I can mail to.
>
> On Wednesday 23 October 2002 15:48, Jim Houston wrote:
> > 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.
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
> --
> /**************************************************
> ** Mark Salisbury || mbs@mc.com **
> ** If you would like to sponsor me for the **
> ** Mass Getaway, a 150 mile bicycle ride to for **
> ** MS, contact me to donate by cash or check or **
> ** click the link below to donate by credit card **
> **************************************************/
> https://www.nationalmssociety.org/pledge/pledge.asp?participantid=86736
--
George Anzinger george@mvista.com
High-res-timers:
http://sourceforge.net/projects/high-res-timers/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml
prev parent reply other threads:[~2002-10-23 22:30 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
2002-10-23 22:18 ` george anzinger
[not found] ` <200210232112.RAA09961@mc.com>
2002-10-23 22:36 ` george anzinger [this message]
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=3DB7245E.B68D1FF4@mvista.com \
--to=george@mvista.com \
--cc=jim.houston@ccur.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbs@mc.com \
/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