1. 05 Jul, 2007 2 commits
  2. 25 Jun, 2007 1 commit
  3. 20 Jun, 2007 1 commit
  4. 29 Mar, 2007 1 commit
  5. 01 Mar, 2007 2 commits
  6. 15 Dec, 2006 1 commit
  7. 01 Dec, 2006 2 commits
  8. 28 Nov, 2006 1 commit
  9. 24 May, 2006 1 commit
  10. 19 May, 2006 2 commits
  11. 05 Apr, 2006 1 commit
  12. 04 Apr, 2006 1 commit
  13. 30 Mar, 2006 1 commit
    • Robert Ricci's avatar
      prune_unusable_pclasses() now goes through the ptypes of the classes · f8b6a77c
      Robert Ricci authored
      it removes, and decrements the available slot count for every node
      in a pclass that is being removed.
      
      After running prune_unusable_pclasses(), we now do another type check,
      minus the pruned pclasses.
      
      This should enable us to detect more free node problems up front -
      let's say there are 8 vnodes that all want 2 interfaces, but only
      a couple pnodes that have 2: most have 1. The second type check will
      now catch this, since all of the 1-interface pnodes have been pruned.
      f8b6a77c
  14. 25 Jan, 2006 3 commits
  15. 16 Dec, 2005 1 commit
    • Robert Ricci's avatar
      The beginnings of a toy version of assign written in Comet. I'm · ef81939b
      Robert Ricci authored
      working on getting a feeling of whether or not it's feasible to
      implement assign in Comet. I think if it is, it would be a huge win in
      terms of maintainability and extensibility.
      
      So far, it's looking very promising. I'm struggling a bit with the
      syntax, and the lack of an API reference. But, once I figure out how
      to do what I need, it's making a lot of sense.
      
      All this program does so far is try to respect the number of slots on
      physical nodes - ie. not assign more than one vnode to a pnode, but it
      can do arbitrary numbers instead of just 1.
      
      It does not read top/ptop files, doesn't know about types, doesn't try
      to minimize any score, doesn't do features/desires, doesn't know about
      links at all, etc. Like I said, it's the beginnings of a toy program.
      
      It looks to me like what we're going to end up doing is writing a
      program to produce Comet programs. One of the cool things about this
      is that it means we can leave out any constraints, etc. that are not
      relevant to the particular mapping problem at hand. And, it should
      make it easy for us to plug in other search techniques (ie. write the
      obvious ones for certain pathological cases, like snakes and
      trees.)
      ef81939b
  16. 29 Sep, 2005 2 commits
  17. 13 Sep, 2005 1 commit
  18. 01 Sep, 2005 2 commits
  19. 29 Aug, 2005 1 commit
  20. 17 May, 2005 1 commit
  21. 10 May, 2005 2 commits
  22. 23 Feb, 2005 1 commit
  23. 31 Jan, 2005 1 commit
  24. 27 Jan, 2005 1 commit
  25. 26 Jan, 2005 1 commit
  26. 19 Jan, 2005 1 commit
    • Robert Ricci's avatar
      Add support for the set-type-limit command in the ptop file. · 8eaec842
      Robert Ricci authored
      It looks like this:
      set-type-limit <type> <count>
      
      This can be placed anywhere in the ptop file.  It limits the number of
      physical nodes of a given type that an experimenter is allowed to use.
      
      For example, we may limit a user to 10 PCs, or 5 pc850s. In the latter
      case, if the experimenter had simply asked for 10 generic PCs, then we
      will try to find them some mapping of nodes that uses types of PCs
      other than pc850s.
      
      Added a precheck to tell the user up-front if they asked for more
      nodes than they are allowed to use of a given type.
      8eaec842
  27. 17 Aug, 2004 1 commit
  28. 12 Aug, 2004 3 commits
  29. 11 Aug, 2004 1 commit