From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <3115414fc57b1a87c6ffe6744f4a65a0@felloff.net> References: <3115414fc57b1a87c6ffe6744f4a65a0@felloff.net> Date: Thu, 5 May 2016 17:00:54 +0100 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a1146a17e770ef205321a7268 Subject: Re: [9fans] A couple questions about /dev/draw and /dev/kbmap Topicbox-Message-UUID: 8ea0452c-ead9-11e9-9d60-3106f5b1d025 --001a1146a17e770ef205321a7268 Content-Type: text/plain; charset=UTF-8 On 5 May 2016 at 14:56, wrote: > libdraw determines the iounit in initdraw() and sizes > its write buffer accordingly. uploading pixels into a image > will split the y/Y operation in multiple ones so they fit > into the buffer. > Yes, and the data doesn't go through rio (unlike an older system), but to /dev/draw, so in the local graphics case the kernel is pulling the draw data directly from the client memory: it doesn't go through 9p. If /dev/draw is imported from a remote system, the local system will generate the 9p, and the remote will receive that, turn round and access its /dev/draw. --001a1146a17e770ef205321a7268 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 5 May 2016 at 14:56, <cinap_lenrek@felloff.net> w= rote:
case the kernel is pulling the= draw data directly from the client memory: it doesn't go through 9p.
If /dev/draw is imported from a remote syste= m, the local system will generate the 9p, and the remote
will receive that, turn round and access its /dev/draw.
=
--001a1146a17e770ef205321a7268--