All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@innominate.de>
To: Keith Owens <kaos@ocs.com.au>, linux-kernel@vger.kernel.org
Subject: Re: Where did vm_operations_struct->unmap in 2.4.0 go?
Date: Fri, 12 Jan 2001 13:01:12 +0100	[thread overview]
Message-ID: <3A5EF208.4013B5F7@innominate.de> (raw)
In-Reply-To: <20010112031247.E10035@nightmaster.csn.tu-chemnitz.de> <24827.979266656@kao2.melbourne.sgi.com>

Keith Owens wrote:
> I want to completely remove this multi layered method for setting
> initialisation order and go back to basics.  I want the programmer to
> say "initialise E and F after G, H and I".  The kernel build system
> works out the directed graph of initialisation order then controls the
> execution of startup code to satisfy this graph.

I don't doubt you will come up with a workable solution at build time. 
However, working out a valid graph at execution time is trivial and
efficient, given a list of precedence relations of the kind you're
suggesting.  In fact you don't even have to work out the graph before
starting the initialization, it's also trivial to keep a count of
unsatisfied initialization conditions at the beginning of each
initialization sequence and block until the count goes to zero.  (In
essence, evaluate a priority sort on the fly.)

--
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2001-01-12 12:04 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-10  3:27 Where did vm_operations_struct->unmap in 2.4.0 go? Allen Unueco
2001-01-10  3:50 ` Keith Owens
2001-01-11  5:38 ` Antony Suter
2001-01-11  6:05   ` Keith Owens
2001-01-11 11:42     ` David Woodhouse
2001-01-11 12:12       ` Keith Owens
2001-01-11 12:32         ` David Woodhouse
2001-01-11 12:46           ` Keith Owens
2001-01-11 13:09             ` Alan Cox
2001-01-11 13:14               ` Keith Owens
2001-01-12  2:12                 ` Ingo Oeser
2001-01-12  2:30                   ` Keith Owens
2001-01-12 10:27                     ` David Woodhouse
2001-01-12 11:55                       ` Keith Owens
2001-01-12 13:40                         ` David Woodhouse
2001-01-12 12:01                     ` Daniel Phillips [this message]
2001-01-12 12:18                       ` Keith Owens
2001-01-14 10:16                         ` Kai Henningsen
2001-01-11 13:25             ` David Woodhouse
     [not found] <3A5EFC56.F1A5BCE0@mira.net>
2001-01-12 19:11 ` Christian Zander
2001-01-13  1:11   ` Keith Owens
2001-01-13 10:46     ` David Woodhouse
2001-01-13 12:06       ` Keith Owens
2001-01-13 15:09         ` David Woodhouse
2001-01-13 19:03           ` Russell King
2001-01-14  0:21           ` Keith Owens
2001-01-14  9:43             ` David Woodhouse
2001-01-14 10:05               ` Keith Owens
2001-01-14 10:45                 ` David Woodhouse
2001-01-14  4:04           ` Linus Torvalds
2001-01-14 17:46             ` David Woodhouse
2001-01-14 19:12               ` Linus Torvalds
2001-01-14 20:02                 ` David Woodhouse
2001-01-14 20:15                   ` Linus Torvalds
2001-01-14 21:15                     ` David Woodhouse
2001-01-14 21:47                       ` Linus Torvalds
2001-01-14 21:57                         ` David Woodhouse
2001-01-14 23:00                         ` Keith Owens
2001-01-15  9:09                           ` David Woodhouse
2001-01-13 11:46     ` Christian Zander
2001-01-13 12:23       ` Keith Owens

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=3A5EF208.4013B5F7@innominate.de \
    --to=phillips@innominate.de \
    --cc=kaos@ocs.com.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.