From: Jeff Epler <jepler@unpythonic.net>
To: Philipp Lutz <philipp.lutz@dlr.de>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: [RFC 0/4] Improving SPI driver latency (vs v3.8.13.14-rt31)
Date: Mon, 1 Sep 2014 13:13:28 -0500 [thread overview]
Message-ID: <20140901181328.GB81857@unpythonic.net> (raw)
In-Reply-To: <540493AA.2020207@dlr.de>
On Mon, Sep 01, 2014 at 05:41:30PM +0200, Philipp Lutz wrote:
> Have you looked into setting a RTPRIO for the SPI worker threads
> (spi_init_queue() in spi.c)? As far as I see hardly any SPI
> hardware-dependent driver sets the "rt" property in the respective
> spi_master struct, so that the main SPI driver (spi.c) will not use a RT
> priority, which will be MAX_RT_PRIO - 1.
Sort of.
I was unaware of the "rt" property so I never tried setting it on the
kernel side. However, I did run into the idea of using "chrt" on the
kernel tasks [spi1] and [irq/99-spi-s3c6]. This improved things
somewhat, but this plus eliminating DMA acquistion still left me with
some 800+us latencies that I didn't want.
(it may have also helped somewhat to to use cpuset to bind these tasks
to the same CPU where my realtime task runs--the U3 is a 4-core chip,
and linuxcnc binds to the last CPU by default)
Jeff
next prev parent reply other threads:[~2014-09-01 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 14:30 [RFC 0/4] Improving SPI driver latency (vs v3.8.13.14-rt31) Jeff Epler
2014-09-01 14:30 ` [PATCH 1/4] spi: reenable sync SPI transfers Jeff Epler
2014-09-01 14:30 ` [PATCH 2/4] spidev: Avoid runtime memory allocations Jeff Epler
2014-09-01 14:30 ` [PATCH 3/4] spidev: actually use synchronous transfers Jeff Epler
2014-09-01 14:30 ` [PATCH 4/4] spidev-s3c64xx: allocate dma channel at startup Jeff Epler
2014-09-01 15:41 ` [RFC 0/4] Improving SPI driver latency (vs v3.8.13.14-rt31) Philipp Lutz
2014-09-01 18:13 ` Jeff Epler [this message]
2014-09-01 22:30 ` Harry van Haaren
2014-09-09 20:01 ` Uwe Kleine-König
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=20140901181328.GB81857@unpythonic.net \
--to=jepler@unpythonic.net \
--cc=linux-rt-users@vger.kernel.org \
--cc=philipp.lutz@dlr.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;
as well as URLs for NNTP newsgroup(s).