Re: [PATCH_TAKE_2] now < last_tick problem

From: David Mosberger <davidm_at_napali.hpl.hp.com>
Date: 2003-10-15 02:58:14
>>>>> On Tue, 14 Oct 2003 15:53:15 +1000, Ian Wienand <ianw@gelato.unsw.edu.au> said:

  Ian> On Mon, Oct 13, 2003 at 10:23:39PM -0700, David Mosberger
  Ian> wrote:
  >> consistency-check.  May want to add a comment about that, though.

  Ian> A few messages up I added something like

  Ian> + * Return the number of nano-seconds that elapsed since the
  Ian> last + * update to jiffy.  It is quite possible that the timer
  Ian> interrupt + * will interrupt this and result in a race for any
  Ian> of jiffies, + * wall_jiffies or itm_next.  Thus, the xtime_lock
  Ian> must be at least + * read-locked when calling this routine.

  Ian> although read-locked should probably be 'read synchronised' or
  Ian> something to avoid confusion.

Sounds fine to me.  Do you want to send me a complete patch so you'll
get the proper credit?

Thanks,

	--david
-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Received on Tue Oct 14 13:04:36 2003

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:19 EST