All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Lockhart <Thomas.Lockhart@domain.hid>
To: Alexis Berlemont <berlemont.hauw@domain.hid>
Cc: Peter Pastor Sampedro <pastorsa@domain.hid>,
	"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] Analogy DIO speed
Date: Thu, 18 Feb 2010 14:48:04 -0800	[thread overview]
Message-ID: <4B7DC3A4.7000503@domain.hid> (raw)
In-Reply-To: <4B7DC07C.5@domain.hid>

>  It is not that bad, no ? Does anybody have an accurate idea on the
>  duration of a common ioctl on such a powerful machine ?

Yikes! My limited and possibly out of date understanding of the PCI bus 
would say that you risk a much larger latency and jitter in just getting 
access to the bus. I'd be happy with anything in the 1us range (1-5?) 
which afaicr is what it takes to negotiate the bus and to write one or a 
few longwords to a device. This is without something already on the bus 
doing DMA or some other block transfer which could push up the latency 
much higher since a block transfer is not required to give up the bus 
for some larger amount of time (please excuse my possible mangled use of 
terms which may have other specific meaning in the PCI spec).

If folks expect much better performance (perhaps from modern revs of 
PCI??) I'd like to hear of their experience...

                                   - Tom



  reply	other threads:[~2010-02-18 22:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-17 21:23 [Xenomai-core] Analogy DIO speed Stefan Schaal
2010-02-18 22:34 ` Alexis Berlemont
2010-02-18 22:48   ` Thomas Lockhart [this message]
2010-02-19  5:43   ` Stefan Schaal
2010-02-23 23:22     ` Alexis Berlemont
2010-03-01  0:24       ` Alexis Berlemont
2010-03-02 18:00         ` Stefan Schaal
2010-03-03 23:58           ` Alexis Berlemont
2010-03-04  0:54             ` Stefan Schaal
2010-03-04  8:37               ` Alexis Berlemont

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=4B7DC3A4.7000503@domain.hid \
    --to=thomas.lockhart@domain.hid \
    --cc=berlemont.hauw@domain.hid \
    --cc=pastorsa@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.