1. 16 Jul, 2002 1 commit
    • Roger Dingledine's avatar
      Implemented link padding and receiver token buckets · 117cbeea
      Roger Dingledine authored
      Each socket reads at most 'bandwidth' bytes per second sustained, but
      can handle bursts of up to 10*bandwidth bytes.
      
      Cells are now sent out at evenly-spaced intervals, with padding sent
      out otherwise. Set Linkpadding=0 in the rc file to send cells as soon
      as they're available (and to never send padding cells).
      
      Added license/copyrights statements at the top of most files.
      
      router->min and router->max have been merged into a single 'bandwidth'
      value. We should make the routerinfo_t reflect this (want to do that,
      Mat?)
      
      As the bandwidth increases, and we want to stop sleeping more and more
      frequently to send a single cell, cpu usage goes up. At 128kB/s we're
      pretty much calling poll with a timeout of 1ms or even 0ms. The current
      code takes a timeout of 0-9ms and makes it 10ms. prepare_for_poll()
      handles everything that should have happened in the past, so as long as
      our buffers don't get too full in that 10ms, we're ok.
      
      Speaking of too full, if you run three servers at 100kB/s with -l debug,
      it spends too much time printing debugging messages to be able to keep
      up with the cells. The outbuf ultimately fills up and it kills that
      connection. If you run with -l err, it works fine up through 500kB/s and
      probably beyond. Down the road we'll want to teach it to recognize when
      an outbuf is getting full, and back off.
      
      
      svn:r50
      117cbeea
  2. 15 Jul, 2002 3 commits
  3. 12 Jul, 2002 4 commits
  4. 11 Jul, 2002 3 commits
  5. 10 Jul, 2002 7 commits
  6. 09 Jul, 2002 2 commits
  7. 08 Jul, 2002 1 commit
    • Roger Dingledine's avatar
      put in the support for 'router twins' · 0a3da3ae
      Roger Dingledine authored
      basically, a twin is a router which is different except it shares
      the same keypair. so in cases where we want to find a "next router"
      and all we really care is that it can decrypt the next onion layer,
      then a twin is just as good.
      
      we still need to decide how to mark twins in the routerinfo_t and in
      the routers config file.
      
      
      svn:r30
      0a3da3ae
  8. 05 Jul, 2002 1 commit
  9. 03 Jul, 2002 4 commits
  10. 02 Jul, 2002 7 commits
  11. 30 Jun, 2002 1 commit
  12. 29 Jun, 2002 5 commits
    • Felipe Bergo's avatar
      added some header checks · e6f67fb1
      Felipe Bergo authored
      
      svn:r16
      e6f67fb1
    • Roger Dingledine's avatar
      ./autogen.sh runs auto* and then ./configure · dcc9fa86
      Roger Dingledine authored
      It should be all you need to do to get working Makefiles on your
      platform, whatever your platform is. :)
      
      Let me know if it doesn't generate Makefiles for you. There will still
      be some bugs to work out in detecting openssl correctly, in checking for
      only the right header files, etc. But we're on our way.
      
      
      svn:r15
      dcc9fa86
    • Roger Dingledine's avatar
      More cleanup. Thanks for your help, Felipe. · 35f90b78
      Roger Dingledine authored
      
      svn:r14
      35f90b78
    • Felipe Bergo's avatar
      added acconfig.h to fix incompatibility · de76e4b9
      Felipe Bergo authored
      
      svn:r13
      de76e4b9
    • Roger Dingledine's avatar
      First cut at cleaning out a lot of the extra stuff. · bd627daa
      Roger Dingledine authored
      The summary here is that I'm requiring all developers to have
      auto* (aclocal, autoconf, automake) installed on their machine.
      
      Since different versions of auto* generate vastly different output,
      I'm going to leave its output out of the repository. This means that
      whenever you check out a repository, you need to run auto* to generate
      a configure file, then run ./configure to get a Makefile, then build.
      
      If you don't have auto* and can't get it, let me know (and I'll try to
      convince you to develop on moria).
      
      The benefit here is that while developers have a bit more work to keep
      things straight, we can build snapshots that will install just about
      anywhere (once we make configure.in work, that is ;)
      
      
      svn:r12
      bd627daa
  13. 28 Jun, 2002 1 commit