Proposal for redesigning the TTY layer



Hello everyone,

Some of you may have already seen some messages on the Perforce list
that I am working on a new branch called `mpsafetty', which will be
primarily focused on removing the Giant lock from the TTY layer, but
will also be used to perform a lot of architectural changes to this part
of the kernel.

The last couple of days I've been working on a document which describes
the changes I'm going to perform. I have just finished this document, so
I'm sending it to this list, so you can give your opinion on this
matter.

As stated in the conclusion of this document, I am willing to continue
development after I graduate. Unfortunately I don't possess all hardware
supported by the TTY layer, which means I could use some help after I
finished by internship to bring back support for the remaining hardware.

I would like to thank the FreeBSD core team for offering me services to
publish my work online, but also the people at Snow B.V. for sponsoring
me in this effort. Thanks!

--
Ed Schouten <ed@xxxxxx>
WWW: http://g-rave.nl/

Attachment: tty-redesign.pdf
Description: Adobe PDF document

Attachment: pgphjU8fIT1jr.pgp
Description: PGP signature



Relevant Pages

  • Re: Proposal for redesigning the TTY layer
    ... supported by the TTY layer, which means I could use some help after I ... finished by internship to bring back support for the remaining hardware. ... So basically I'll need help with the console drivers on the more exotic ...
    (freebsd-arch)
  • Re: rt20 scheduling latency testcase and failure data
    ... The system was under heavy network load for some of the time, ... # Firmware Drivers ... # ACPI Support ... # ISDN4Linux hardware drivers ...
    (Linux-Kernel)
  • NMI watchdog doesnt know what hardware to touch
    ... NMI watchdog doesn't know what hardware to touch ... Linux 2.6.24-rc5-g4af75653 on x86_64 ... # SCSI support type ... # Input Device Drivers ...
    (Linux-Kernel)
  • Re: Linux 2.6.20-rc2
    ... corruption (either hardware or kernel induced) that could cause this. ... So my guess would still be memory corruption of some sort, ... # ACPI Support ...
    (Linux-Kernel)
  • oops during rsync
    ... Hopefully someone can help - I am beginning to believe this is a very intermittent hardware issue... ... then the kernel config and system map. ... # Firmware Drivers ... # ACPI Support ...
    (Linux-Kernel)

Quantcast