Skip to content
Snippets Groups Projects
  1. Jul 06, 2018
  2. Jul 05, 2018
  3. Jun 29, 2018
  4. Jun 18, 2018
  5. May 16, 2018
  6. May 15, 2018
    • David Hancock's avatar
      Updated agilio prep analysis: impact of table limit · 9a6c9d5c
      David Hancock authored
      Current codebase supports the following configurations, where
      the first number is the number of stages supported, and the
      second number is the max number of primitives per stage
      supported:
      - 2 x 9
      - 3 x 8
      - 4 x 5
      - 5 x 4
      - 6 x 3
      - 8 x 2
      - 9 x 1
      ...as well as any configuration smaller in at least one dimension
      than one of the listed configurations.
      9a6c9d5c
    • David Hancock's avatar
      Note results of action count (const 150 regardless of config) · 149332a7
      David Hancock authored
      Number of actions does not change with hp4's configuration in
      terms of the number of stages and primitives supported.  The
      total number of actions is currently 150 and only changes
      as we modify P4 support.  This number is well under Agilio's
      limit of 256 actions.
      149332a7
    • David Hancock's avatar
      Create action counter scripts for HP4 configurations · 4ea8ef2c
      David Hancock authored
      Generates all hp4 configurations 1-X by 1-Y, where X is
      the number of stages supported, and Y is the max number
      of primitives per stage supported.  Then counts the
      total number of actions defined per configuration, and
      collects results across all configurations into a .csv.
      4ea8ef2c
    • David Hancock's avatar
      Add test for select(current(x,y)) return statement support · fca54322
      David Hancock authored
      The test reveals that p4_hp4 does not properly handle
      this type of parser return statement yet; ongoing analysis
      is in tests/analysis/test_select.txt.
      fca54322
  7. May 14, 2018
    • David Hancock's avatar
      Confirm conditions for running tests / no unwanted output · 49f91cf0
      David Hancock authored
      Unwanted output noted in previous commit was result of forgetting
      that the hp4controller modules had been installed to /usr/local/...
      via setuptools (setup.py in hp4-ctrl), so the modules being
      accessed were not the ones I was modifying in my home directory.
      
      To more easily modify these files and run tests, instead of
      using setuptools we modify PYTHONPATH in .profile in the home
      directory.  We must also modify sudoers to preserve the
      environment when running commands via sudo, because the
      test requires the use of sudo, because of mininet.
      
      We should add basic instructions to this effect.
      49f91cf0
  8. May 11, 2018
  9. May 10, 2018
    • David Hancock's avatar
      Complete initial HP4 test framework functionality · 1b1063ca
      David Hancock authored
      Demo: HP4 running test_hub; two tests:
      - h1 ping h2 (expected: success)
      - h1 ping h3 (expected: fail)
      Both tests return the expected results.
      
      To run: sudo ./test.py.
      
      Additional tests may be added with 1-3 files per need:
      - <proj>.p4
      - [<proj>.commands] -- bmv2 runtime table management commands
      - [<proj>.py] -- test cases + mininet script
      
      If the <proj>.py file is not present, the framework uses
      test_mininet.py with the two tests described above (h1 ping h2,
      h1 ping h3).
      1b1063ca
  10. May 07, 2018
  11. Apr 12, 2018
  12. Apr 11, 2018
  13. Dec 04, 2017
    • David Hancock's avatar
      Change modify_field type to remove conflict w/ action handling · 7466a7b8
      David Hancock authored
      Action handling now involves checking whether
      meta_primitive_state.primitive[+Y+] == 0 between primitives,
      which indicates no further primitives remain, but that value
      was used to indicate a modify_field primitive, so the value
      for modify_field has been changed.
      7466a7b8
  14. Dec 01, 2017
  15. Nov 20, 2017
  16. Nov 07, 2017
  17. Nov 05, 2017
    • David Hancock's avatar
      Fix next_table field width to handle MATCHLESS value (99) · 48bacb68
      David Hancock authored
      Also, comments added to help identify conditionals, supporting
      debugging via the event logger.
      
      The next_table field was 4 bits, but init_program_state was
      assigning a value of '99' corresponding to matchless table type.
      When a modify_field tries to assign a value larger than the width
      of the target, bmv2 silently fails.
      
      Over in hp4-ctrl, t06 now works in its most essential test -
      a chain is created with simple_router -> firewall, and the
      router routes, and the firewall blocks/doesn't block correctly!
      48bacb68
  18. Nov 03, 2017
  19. Oct 31, 2017
  20. Oct 30, 2017
    • David Hancock's avatar
      Merge branch 'experimental' · 68b92ba6
      David Hancock authored
      Conflicts:
      	hp4/hp4commands.txt
      	hp4/p4src/includes/parser.p4
      	hp4/p4src/includes/setup.p4
      	hp4/template/includes/parser.p4t
      	hp4/template/includes/setup.p4t
      68b92ba6
    • David Hancock's avatar
      Clean house · 15f8f5a6
      David Hancock authored
      p4c-hp4 belongs to the hp4-ctrl repo.  Script for nano_msg client updated.
      Misc files deleted.
      15f8f5a6
  21. Oct 27, 2017
Loading