@phdthesis{Schneidenbach2009,
  author    = {Schneidenbach, Lars},
  title     = {The benefits of one-sided communication interfaces for cluster computing},
  address   = {Potsdam},
  pages     = {208 S. : graph. Darst.},
  year      = {2009},
  language  = {en}
}
@article{SchneidenbachSchnor2007,
  author    = {Schneidenbach, Lars and Schnor, Bettina},
  title     = {Design Issues in the Implementation of MPI2 One Sided Communication in Ethernet based Networks},
  isbn      = {978-0-88986-637-9},
  year      = {2007},
  abstract  = {In current research, one sided communication of the MPI2 standard is pushed as a promising technique [6, 7, 10, 18]. But measurements of applications and MPI2 primitives show a different picture [17]. In this paper we analyze de sign issues of MPI2 one sided communication and its im plementations. We focus on asynchronous communication for parallel applications in Ethernet cluster environments. Further, one sided communication is compared to two sided communication. This paper will prove that the key problem to performance is not only the implementation of MPI2 one sided communication - it is the design.},
  language  = {en}
}
@article{FriedrichKrahmerSchneidenbachetal.2006,
  author    = {Friedrich, Sven and Krahmer, Sebastian and Schneidenbach, Lars and Schnor, Bettina},
  title     = {Loaded: Server Load Balancing for IPv6},
  isbn      = {0-7695-2622-5},
  year      = {2006},
  abstract  = {With the next generation Internet protocol IPv6 at the horizon, it is time to think about how applications can migrate to IPv6. Web traffic is currently one of the most important applications in the Internet. The increasing popularity of dynamically generated content on the World Wide Web, has created the need for fast web servers. Server clustering together with server load balancing has emerged as a promising technique to build scalable web servers. The paper gives a short overview over the new features of IPv6 and different server load balancing technologies. Further, we present and evaluate Loaded, an user-space server load balancer for IPv4 and IPv6 based on Linux.},
  language  = {en}
}
@article{SchneidenbachSchnor2005,
  author    = {Schneidenbach, Lars and Schnor, Bettina},
  title     = {Migration of MPI Applications to IPv6 Networks},
  isbn      = {0-88986-468-3},
  year      = {2005},
  language  = {en}
}
@article{FriedrichSchneidenbachSchnor2005,
  author    = {Friedrich, Sven and Schneidenbach, Lars and Schnor, Bettina},
  title     = {SLIBNet : Server Load Balancing for InfiniBand Networks},
  year      = {2005},
  abstract  = {Today, InfiniBand is an evolving high speed interconnect technology to build high performance computing clusters, that achieve top 10 rankings in the current top 500 of the worldwide fastest supercomputers. Network interfaces (called host channel adapters) provide transport layer services over connections and datagrams in reliable or unreliable manner. Additionally, InfiniBand supports remote direct memory access (RDMA) primitives that allow for one- sided communication. Using server load balancing together with a high performance cluster makes it possible to build a fast, scalable, and reliable service infrastructure. We have designed and implemented a scalable load balancer for InfiniBand clusters called SLIBNet. Our investigations show that the InfiniBand architecture offers features which perfectly support load balancing. We want to thank the Megware Computer GmbH for providing us an InfiniBand switch to realize a server load balancing testbed.},
  language  = {en}
}
@article{FriedrichKrahmerSchneidenbachetal.2004,
  author    = {Friedrich, Sven and Krahmer, Sebastian and Schneidenbach, Lars and Schnor, Bettina},
  title     = {Loaded : Server Load Balancing for IPv6},
  year      = {2004},
  language  = {en}
}
@article{SchneidenbachSchnorPetri2003,
  author    = {Schneidenbach, Lars and Schnor, Bettina and Petri, Stefan},
  title     = {Architecture and Implementation of the Socket Interface on Top of GAMMA},
  isbn      = {0-7695-2037-5},
  year      = {2003},
  language  = {en}
}