From: Alan Cox <alan@linux.intel.com>
To: Ivo Sieben <meltedpianoman@gmail.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
<linux-serial@vger.kernel.org>,
RT <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH 3/3] RFC: Solved unnecessary schedule latency in the TTY layer (3/3)
Date: Thu, 10 May 2012 16:28:50 +0100 [thread overview]
Message-ID: <20120510162850.3a61702d@bob.linux.org.uk> (raw)
In-Reply-To: <1336048663-21882-3-git-send-email-meltedpianoman@gmail.com>
On Thu, 3 May 2012 14:37:43 +0200
Ivo Sieben <meltedpianoman@gmail.com> wrote:
> Solved unnecessary schedule latency in the TTY layer when used in
> realtime context:
> The global wait_queue that is used for line discipline idle handling
> is moved to a separate wait_queue for each line instance. This
> prevents unnecessary blocking on one line, because of idle handling
> on another line.
>
> Note: In a PREEMPT_RT system "normal" spin locks behave like mutexes
> and no interrupts (and therefor no scheduling) is disabled.
>
> Signed-off-by: Ivo Sieben <meltedpianoman@gmail.com>
And this one as a standalone I think we should merge. I'm surprised it
makes a difference but its small, clean and localises a lock which is a
good thing.
Alan
next prev parent reply other threads:[~2012-05-10 15:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 12:37 [PATCH 1/3] RFC: Solved unnecessary schedule latency in the TTY layer (1/3) Ivo Sieben
2012-05-03 12:37 ` [PATCH 2/3] RFC: Solved unnecessary schedule latency in the TTY layer (2/3) Ivo Sieben
2012-05-03 16:25 ` Greg KH
2012-05-07 7:45 ` Ivo Sieben
2012-05-03 12:37 ` [PATCH 3/3] RFC: Solved unnecessary schedule latency in the TTY layer (3/3) Ivo Sieben
2012-05-03 16:24 ` Greg KH
2012-05-10 15:28 ` Alan Cox [this message]
2012-05-07 14:10 ` [PATCH 1/3] RFC: Solved unnecessary schedule latency in the TTY layer (1/3) Ivo Sieben
2012-05-10 15:26 ` Alan Cox
2012-05-14 12:25 ` Ivo Sieben
2012-05-15 15:04 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120510162850.3a61702d@bob.linux.org.uk \
--to=alan@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=meltedpianoman@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).