From: Alexander Sverdlin <alexander.sverdlin@gmail.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 3/3] drivers/tty: increase priority for tty_buffer_worker
Date: Mon, 11 Mar 2019 09:24:20 +0100 [thread overview]
Message-ID: <20190311092420.7f57b8e4e3420de225213367@gmail.com> (raw)
In-Reply-To: <20190110101232.9398-4-o.rempel@pengutronix.de>
Hello Oleksij,
On Thu, 10 Jan 2019 11:12:32 +0100
Oleksij Rempel <o.rempel@pengutronix.de> wrote:
> sched_priority = 1 is enough to dramatically reduce latency
> on have system load produced by tasks with default user space prio.
>
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Tested-by: Alexander Sverdlin <alexander.sverdlin@gmail.com>
> ---
> drivers/tty/tty_buffer.c | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/tty/tty_buffer.c b/drivers/tty/tty_buffer.c
> index 18bd7f48a319..7cf42f6570a0 100644
> --- a/drivers/tty/tty_buffer.c
> +++ b/drivers/tty/tty_buffer.c
> @@ -13,11 +13,13 @@
> #include <linux/string.h>
> #include <linux/slab.h>
> #include <linux/sched.h>
> +#include <linux/sched/rt.h>
> #include <linux/wait.h>
> #include <linux/bitops.h>
> #include <linux/delay.h>
> #include <linux/module.h>
> #include <linux/ratelimit.h>
> +#include <uapi/linux/sched/types.h>
>
>
> #define MIN_TTYB_SIZE 256
> @@ -567,7 +569,15 @@ bool tty_buffer_queue_work(struct tty_port *port)
>
> void tty_buffer_init_kthread(void)
> {
> - kthread_run(kthread_worker_fn, &tty_buffer_worker, "tty");
> + struct sched_param param = { .sched_priority = 1 };
> + struct task_struct *kworker_task;
> +
> + kworker_task = kthread_run(kthread_worker_fn, &tty_buffer_worker, "tty");
> + if (IS_ERR(kworker_task)) {
> + pr_err("failed to create message pump task\n");
> + return;
> + }
> + sched_setscheduler(kworker_task, SCHED_FIFO, ¶m);
> }
>
> /**
--
Alexander Sverdlin.
next prev parent reply other threads:[~2019-03-11 8:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 10:12 [PATCH v1 0/3] reduce tty latency Oleksij Rempel
2019-01-10 10:12 ` [PATCH v1 1/3] drivers/tty: refactor functions for flushing/queuing work Oleksij Rempel
2019-03-11 8:16 ` Alexander Sverdlin
2019-01-10 10:12 ` [PATCH v1 2/3] drivers/tty: convert tty_port to use kthread_worker Oleksij Rempel
2019-03-11 8:23 ` Alexander Sverdlin
2019-01-10 10:12 ` [PATCH v1 3/3] drivers/tty: increase priority for tty_buffer_worker Oleksij Rempel
2019-01-10 12:54 ` Linus Torvalds
2019-01-10 15:19 ` Oleksij Rempel
2019-01-10 16:30 ` Greg Kroah-Hartman
2019-01-28 8:05 ` Oleksij Rempel
2019-01-28 8:23 ` Greg Kroah-Hartman
2019-01-28 9:22 ` Oleksij Rempel
2019-01-28 20:03 ` Linus Torvalds
2019-01-28 20:13 ` Linus Torvalds
2019-01-10 16:59 ` Linus Torvalds
2019-03-11 8:24 ` Alexander Sverdlin [this message]
2019-01-10 13:51 ` [PATCH v1 0/3] reduce tty latency Greg Kroah-Hartman
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=20190311092420.7f57b8e4e3420de225213367@gmail.com \
--to=alexander.sverdlin@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
/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