From: Wolfgang Grandegger <wg@domain.hid>
To: rolandtollenaar@domain.hid
Cc: xenomai-help <xenomai@xenomai.org>
Subject: [Xenomai-help] Re: Latencies due to RT-Socket-CAN register accesses
Date: Wed, 14 Mar 2007 10:33:04 +0100 [thread overview]
Message-ID: <45F7C150.4030707@domain.hid> (raw)
In-Reply-To: <45F6AA11.40707@domain.hid>
Roland Tollenaar wrote:
> HI Wolfgang,
>
>> It was the IXXAT PCI card currently plugged into my test PC but I
>> actually recommand the PEAK PCI card. It's also much cheaper, I guess.
>> Tomorrow I'm going to repeat the tests with this card ... stay tuned.
> Clear. Thanks for the advice.
Here is a revised list of the register access times:
PEAK-Dongle: register read : 11705ns ( 85428/sec)
PEAK-Dongle: register write: 11687ns ( 85562/sec)
IXXAT-PCI : register read : 725ns (1378643/sec)
IXXAT-PCI : register write: 301ns (3311667/sec)
PEAK-PCI : register read : 486ns (2057468/sec)
PEAK-PCI : register write: 161ns (6201956/sec)
>>> I will continue development on my laptop with the dongle for the time
>>> being. It would be interesting to see what happens to the latency
>>> after your proposed changes are in effect.
Non-CAN latencies will not be significantly affected but RT-Socket-CAN
latencies will be worse due to overhead of interrupt handling by the
service task.
>> BTW, what are the latencies you measure on your system under load
>> (without RT-Socket-CAN).
> Off the top of my head 25us average 30us to 35us max. I am not sure I am
> "loading" the system though. How do I measure this load that is always
> talked about?
>
> Roland
>
>
>>
>> Wolfgang.
>>
>>> Thanks,
>>>
>>> Roland
>>>
>>>
>>>
>>> Wolfgang Grandegger wrote:
>>>> Hallo,
>>>>
>>>> in the meantime I have measured the latencies introduced through
>>>> messages sent and received by RT-Socket-CAN. The SJA1000 register
>>>> access times on my rather old PC with an Athlon 1100 Mhz are:
>>>>
>>>> PEAK-Dongle: read access: 11807 ns
>>>> PEAK-Dongle: write access: 11677 ns
>>>>
>>>> IXXAT-PCI : read access: 729 ns
>>>> IXXAT-PCI : write access: 305 ns
>>>>
>>>> I measured an increase of the latency of approx. 170us with the
>>>> PEAK-Dongle and approx 13us with the IXXAT-PCI card for the
>>>> reception of a full CAN message (with 8 bytes payload). Sending
>>>> messages is a bit less disturbing. I have attached a small patch to
>>>> measure the SJA1000 register access times when the driver is
>>>> initialized. You are welcome to apply it on your setup and report
>>>> the results. I'm especially interested in numbers for the ISA bus
>>>> (or PC-104).
>>>>
>>>> Wolfgang.
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>> + diff -u xenomai/ksrc/drivers/can/rtcan_dev.c.IOTEST
>>>> xenomai/ksrc/drivers/can/rtcan_dev.c
>>>> + diff -u xenomai/ksrc/drivers/can/sja1000/rtcan_sja1000.c.IOTEST
>>>> xenomai/ksrc/drivers/can/sja1000/rtcan_sja1000.c
>>>> --- xenomai/ksrc/drivers/can/sja1000/rtcan_sja1000.c.IOTEST
>>>> 2007-02-26 09:17:27.000000000 +0100
>>>> +++ xenomai/ksrc/drivers/can/sja1000/rtcan_sja1000.c 2007-03-13
>>>> 10:01:47.000000000 +0100
>>>> @@ -728,6 +728,30 @@
>>>> if (chip == NULL)
>>>> return -EINVAL;
>>>>
>>>> +#if 1
>>>> + {
>>>> + nanosecs_abs_t begin, diff;
>>>> + volatile u8 reg;
>>>> + int i, count = 100000;
>>>> + begin = rtdm_clock_read();
>>>> + for (i = 0; i < count; i++) {
>>>> + reg = chip->read_reg(dev, 0);
>>>> + }
>>>> + diff = rtdm_clock_read() - begin;
>>>> + printk("%s: register read time for %d accessed: %ld (%ld per
>>>> access)\n",
>>>> + dev->board_name, count,
>>>> + (unsigned long)diff, (unsigned long)diff / count);
>>>> + begin = rtdm_clock_read();
>>>> + for (i = 0; i < count; i++) {
>>>> + chip->write_reg(dev, 0, reg);
>>>> + }
>>>> + diff = rtdm_clock_read() - begin;
>>>> + printk("%s: register write time for %d accessed: %ld (%ld per
>>>> access)\n",
>>>> + dev->board_name, count,
>>>> + (unsigned long)diff, (unsigned long)diff / count);
>>>> + }
>>>> +#endif
>>>> +
>>>> /* Set dummy state for following call */
>>>> dev->state = CAN_STATE_ACTIVE;
>>>> /* Enter reset mode */
>>>
>>>
>>
>>
>
>
next prev parent reply other threads:[~2007-03-14 9:33 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 10:52 [Xenomai-help] Latencies due to RT-Socket-CAN register accesses Wolfgang Grandegger
2007-03-13 13:16 ` [Xenomai-help] " Roland Tollenaar
2007-03-13 13:29 ` Wolfgang Grandegger
2007-03-13 13:41 ` Roland Tollenaar
2007-03-13 14:06 ` Wolfgang Grandegger
2007-03-14 9:33 ` Wolfgang Grandegger [this message]
2007-03-28 17:05 ` roland Tollenaar
2007-03-28 18:50 ` Wolfgang Grandegger
2007-03-29 2:17 ` Roland Tollenaar
2007-03-29 8:38 ` Stéphane ANCELOT
2007-03-29 8:59 ` Wolfgang Grandegger
2007-03-29 16:44 ` Roland Tollenaar
2007-03-29 18:51 ` Gilles Chanteperdrix
2007-03-29 18:59 ` Wolfgang Grandegger
2007-04-23 15:09 ` [Xenomai-help] " roland Tollenaar
2007-04-23 18:28 ` Gilles Chanteperdrix
2007-04-24 8:44 ` roland Tollenaar
2007-04-24 8:56 ` Gilles Chanteperdrix
2007-04-24 10:27 ` roland Tollenaar
2007-04-24 10:27 ` roland Tollenaar
2007-04-24 12:57 ` Gilles Chanteperdrix
2007-04-24 18:36 ` roland Tollenaar
2007-04-24 9:05 ` Jan Kiszka
2007-04-24 10:31 ` roland Tollenaar
2007-04-24 10:51 ` Jan Kiszka
2007-04-24 12:14 ` roland Tollenaar
2007-04-24 12:32 ` Jan Kiszka
2007-04-24 10:57 ` Wolfgang Grandegger
2007-04-24 11:00 ` Jan Kiszka
2007-04-24 12:17 ` roland Tollenaar
2007-04-24 12:19 ` roland Tollenaar
2007-04-24 12:44 ` Wolfgang Grandegger
2007-04-25 9:04 ` Stéphane ANCELOT
2007-04-25 11:02 ` Roland Tollenaar
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=45F7C150.4030707@domain.hid \
--to=wg@domain.hid \
--cc=rolandtollenaar@domain.hid \
--cc=xenomai@xenomai.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.