fa5bd71218
given that devmnt will almost always write into a pipe or a network connection, which supports te bwrite routine, we can avoid the memory copy that would have been done by devbwrite(). this also means the i/o buffer for writes will get freed sooner without having to wait for the 9p rpc to get a response, saving memory. theres one case where we have to keep the rpc arround and that is when we write to a cached file, as we want to update the cache with the data that was written, but the user buffer cannot be trusted to stay the same during the rpc. |
||
|---|---|---|
| .. | ||
| bcm | ||
| boot | ||
| ip | ||
| kw | ||
| mtx | ||
| omap | ||
| pc | ||
| pc64 | ||
| port | ||
| ppc | ||
| sgi | ||
| teg2 | ||
| xen | ||
| zynq | ||
| mkfile | ||