In thinking about experimenting with Solaris networking, I was pondering how I could experiment with using different types of buffer allocation schemes behind STREAMS.
Allocating buffers seems to be done by the driver calling: - allocb - esballoc - desballoc - copyb - dupb - others? What I'd like to do is take control of how they allocate blocks, perhaps even supply my own base rather and override input from *esballoc or even imitate failures. The parameters into the buffer allocation would ideally be: - size of buffer - priority - driver name and instance wanting it (hard/impossible?) Of couse this would allow base (in esballoc/desballoc) to be ignored. Why would I care about driver name & instance? Because I might want to use a different buffer allocation strategy for ce0 than for ppp0. And I mention driver name/instance because I don't think this capability should be tied to any specific network protocol. If it matters, something like dladm is what I'd envisage being the appropriate management interface. Is this doable? Darren _______________________________________________ networking-discuss mailing list [email protected]
