Giter Club home page Giter Club logo

ipd's People

Contributors

citrus-it avatar felixmcfelix avatar gdamore avatar hadfl avatar hrosenfeld avatar jasonbking avatar jclulow avatar jlevon avatar pfmooney avatar pjrobar avatar ptribble avatar r1mikey avatar richlowe avatar rmustacc avatar rzezeski avatar tsoome 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

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  avatar

ipd's Issues

IPD 6 feedback from Garrett

Tagging @gdamore, as he emailed me, and I'm long overdue putting it in the public record. The following text is his:

. . .

On allocb() using a less persistent attempt (and esballoc() and desballoc()):

I’m in favor of adding this as an option for NIC drivers. Most ethernet drivers can gracefully deal with packet loss, and this is indeed preferable to trying extra hard to allocate a packet. So for ethernet (and WIFI) drivers in particular, KM_NORMALPRI is preferable. (Note that this won’t apply to all NIC drivers. Note also that esballoc and desballoc are probably exclusively, or nearly so, used by NIC drivers trying to minimize DMA losses.)

Other places are less forgiving.

Our console, HID (keyboards, mice, etc.) and USB stacks use mblks. These are less likely to be forgiving of allocation failure. They shouldn’t be impacted.
IP is forgiving. But, at the same time if we’ve already paid the cost to obtain the packet from the hardware (which is likely not to be trivial), we probably don’t want to be too aggressive in dropping the packet. I’d vote for not using KM_NORMALPRI for things in the middle portion of the stack as a result.
For the same reasons in # 2, I would not use KM_NORMALPRI in msgpullup/pullupmsg.

So, to recap, I’d have it be opt-in, and only done in the receive routines for device drivers that can easily cope with it.

(Hmm… it might be a good idea to do this for allocb()’s that are used when looping back mblks sent downstream for promiscuous devices… I can see arguments both way in that case.)

. . .

Need firm definitions of pre-draft, draft, published

There is no solid definitions of the IPD states. For example, one could assume:

Pre-draft: Still so WIP that readers should expect document changes in the short term.

Draft: Document is "good" and needs to be implemented. Could be changed only in the face of implementation/bringup experience.

Published: Document reflects running code.

For example, IPD 6 is in pre-draft state, but is much further along than, say, a skeletal IPD like IPD 11 is as of the time of this issue's filing. IPD 6 has open questions, but once answered is good to implement.

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.