Giter Club home page Giter Club logo

perfbook's People

Contributors

akiyks avatar alanskind avatar anatol avatar bonzini avatar bp3tk0v avatar bsingharora avatar cota avatar cppfool avatar elahav avatar eliedebrauwer avatar fbq avatar juerd avatar junchangwang avatar kljohann avatar kraai avatar leobras avatar namhyung avatar patrick-yingxi-pan avatar paulmckrcu avatar pierrekuo2git avatar rfabbri avatar shenki avatar sjp38 avatar stamatis avatar suryasaimadhu avatar teg avatar tklauser avatar walkerlala avatar wfp5p avatar zhouzhouyi-hub avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

perfbook's Issues

[whymb] Missing writeback

Before CPU0 can mark its cache line as "shared", the line must be written back to main memory to prevent data loss. It is worth mentioning here as long as we are concerned with main memory at all.

\item CPU~0 receives the ``read'' message, and transmits the
cache line containing the now-updated value of ``b''
to CPU~1, also marking the line as ``shared'' in its own cache.
\item CPU~1 receives the cache line containing ``b'' and installs
it in its cache.

\item CPU~0 receives the ``acknowledgement'' message, and puts
the cache line containing ``b'' into the ``exclusive'' state.
CPU~0 now stores the new value of ``b'' into the cache line.
\item CPU~0 receives the ``read'' message, and transmits the
cache line containing the new value of ``b''
to CPU~1.
It also marks its own copy of this cache line as ``shared''.

Error 127 is not a good error message

this happen when inkscape crashs, could you to change for a better expressive message ?
advsync/irq.svg --> advsync/irq.pdf
make: *** [Makefile:467: advsync/irq.pdf] Error 127

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.