| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] [PATCH] Console Daemon
> It only really needs to be big enough to absorb all the messages before
> Linux's console buffering code comes up, which isn't very much,
> certainly <4KB.
>
> My view is that we should continue using the same buffer once xenbus
> comes up, hence there should be a simple multiplexing protocol.
The kernel will end up allocating a buffer per console anyway, usually
at least a page in size. May as well just make that buffer visible via
xenstore and have console daemon directly pull the bytes out of it.
This also avoids the need for framing infomation, so no packet-ising
of data within the console ring buffers, which also makes recovery and
suspend/resume somewhat easier (no need to resync ring indexes -- the
new/restarted daemon can just start reading out of the ring buffer
where the previous daemon left off with no potentially fragile
recover/restart protocol).
Bottom line: I'd like simple, correct and highly available console
ahead of features like multi-headed console driver or xenbus-enabled
console.
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home