Re: [PATCH] Use tty_schedule in VT code.

O> In that case, we might as well just always do the scheduled_delayed_work() 
> with a zero timeout as per the earlier patch. I'd still like to know who 
> *cares*, though? Why not leave it at 1?

I don't think it really matters too much on modern systems so long as we
keep the flush_to_ldisc out of IRQ context. Historically we tried to
batch the ldisc processing but I doubt any modern box cares too much
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH] Use tty_schedule in VT code.
    • From: James Simmons <[email protected]>
  • Re: [PATCH] Use tty_schedule in VT code.
    • From: Linus Torvalds <[email protected]>
  • Re: [PATCH] Use tty_schedule in VT code.
    • From: Paul Fulghum <[email protected]>
  • Re: [PATCH] Use tty_schedule in VT code.
    • From: Linus Torvalds <[email protected]>
  • Re: [PATCH] Use tty_schedule in VT code.
    • From: James Simmons <[email protected]>
  • Re: [PATCH] Use tty_schedule in VT code.
    • From: Linus Torvalds <[email protected]>

• Prev by Date: Re: [PATCH] change SysRq keycode for systems without SysRq key
• Next by Date: Re: [PATCH][RFC] 4K stacks default, not a debug thing any more...?
• Previous by thread: Re: [PATCH] Use tty_schedule in VT code.
• Next by thread: Re: [PATCH] Use tty_schedule in VT code.
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]