• Documents
  • Authors
  • Tables
  • Log in
  • Sign up
  • MetaCart
  • DMCA
  • Donate

CiteSeerX logo

Advanced Search Include Citations
Advanced Search Include Citations

DMCA

Eliminating receive livelock in an interrupt-driven kernel (1997)

Cached

  • Download as a PDF

Download Links

  • [cs.unomaha.edu]
  • [www.stanford.edu]
  • [pdos.csail.mit.edu]
  • [pdos.lcs.mit.edu]
  • [www.cs.utexas.edu]
  • [www.news.cs.nyu.edu]
  • [www.cs.utexas.edu]
  • [www.pdos.lcs.mit.edu]
  • [pdos.csail.mit.edu]
  • [www.cs.brown.edu]
  • [www.cs.brown.edu]
  • [pdos.lcs.mit.edu]
  • [cs.brown.edu]
  • [cs.brown.edu]
  • [pdos.csail.mit.edu]
  • [www.news.cs.nyu.edu]
  • [pdos.csail.mit.edu]
  • [dcslab.snu.ac.kr]
  • [ftp.digital.com]
  • [cs.nyu.edu]
  • [www.cs.utexas.edu]
  • [www.cs.ucla.edu]
  • [www.hpl.hp.com]

  • Other Repositories/Bibliography

  • DBLP
  • Save to List
  • Add to Collection
  • Correct Errors
  • Monitor Changes
by Jeffrey Mogul , Dec Western , Jeffrey C. Mogul , K. K. Ramakrishnan
Venue:ACM Transactions on Computer Systems
Citations:321 - 5 self
  • Summary
  • Citations
  • Active Bibliography
  • Co-citation
  • Clustered Documents
  • Version History

BibTeX

@ARTICLE{Mogul97eliminatingreceive,
    author = {Jeffrey Mogul and Dec Western and Jeffrey C. Mogul and K. K. Ramakrishnan},
    title = {Eliminating receive livelock in an interrupt-driven kernel},
    journal = {ACM Transactions on Computer Systems},
    year = {1997},
    volume = {15},
    pages = {217--252}
}

Share

Facebook Twitter Reddit Bibsonomy

OpenURL

 

Abstract

Most operating systems use interface interrupts to schedule network tasks. Interrupt-driven systems can provide low overhead and good latency at low of-fered load, but degrade significantly at higher arrival rates unless care is taken to prevent several pathologies. These are various forms of receive livelock, in which the system spends all its time processing interrupts, to the exclusion of other neces-sary tasks. Under extreme conditions, no packets are delivered to the user application or the output of the system. To avoid livelock and related problems, an operat-ing system must schedule network interrupt handling as carefully as it schedules process execution. We modified an interrupt-driven networking implemen-tation to do so; this eliminates receive livelock without degrading other aspects of system performance. We present measurements demonstrating the success of our approach. 1.

Keyphrases

receive livelock    interrupt-driven kernel    good latency    interrupt-driven system    several pathology    low of-fered load    network interrupt handling    various form    process execution    low overhead    system performance    extreme condition    interrupt-driven networking implemen-tation    interface interrupt    present measurement    neces-sary task    user application    related problem    time processing interrupt    network task    arrival rate    operat-ing system   

Powered by: Apache Solr
  • About CiteSeerX
  • Submit and Index Documents
  • Privacy Policy
  • Help
  • Data
  • Source
  • Contact Us

Developed at and hosted by The College of Information Sciences and Technology

© 2007-2019 The Pennsylvania State University