linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 1/3] RFC: Solved unnecessary schedule latency in the TTY layer (1/3)
Date: Thu, 10 May 2012 16:26:21 +0100	[thread overview]
Message-ID: <20120510162621.4b5d7907@bob.linux.org.uk> (raw)
In-Reply-To: <1336048663-21882-1-git-send-email-meltedpianoman@gmail.com>

> 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>

(Coming back round to these patches now the urgent stuff is buried for
a bit)

>  void tty_schedule_flip(struct tty_struct *tty)
>  {
> -	unsigned long flags;
> -	spin_lock_irqsave(&tty->buf.lock, flags);
> -	if (tty->buf.tail != NULL)
> -		tty->buf.tail->commit = tty->buf.tail->used;
> -	spin_unlock_irqrestore(&tty->buf.lock, flags);
> -	schedule_work(&tty->buf.work);
> +	tty_flip_buffer_push(tty);
>  }

You'd need to ifdef both of these for non RT cases. I think it may be
right for RT although I'm not 100% sure on the locking.

At this point I think we'd be better off sorting out our tty locking in
general before tackling RT optimisations. However as an RT patch it
looks good and its interesting to see RT simplifying code not making it
more complex.

  parent reply	other threads:[~2012-05-10 15:11 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
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 [this message]
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=20120510162621.4b5d7907@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).