All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Cromie <jim.cromie@domain.hid>
To: xenomai-core <xenomai@xenomai.org>
Subject: [Xenomai-core] kconfig help questions
Date: Sun, 07 May 2006 23:22:04 -0400	[thread overview]
Message-ID: <445EB95C.6050302@domain.hid> (raw)


Going thru xenomai Kconfig again, some observations/uncertainties came up.
I'll make a patch, given feedback.

XENO_OPT_TIMING_PERIODIC

"Aperiodic mode provides for non-constant delays between timer ticks,"

the wording here (non-constant delays) left me momentarily wondering
if _APERIODIC was bad (this, despite the use of 'provides'). 
Maybe "sub-tick delays" makes some sense ..

XENO_OPT_SHIRQ_LEVEL

Are there any decent estimates or examples of the latency / jitter increases
if this is enabled ?  Is it highly cpu or chipset dependent ?
I presume /proc/interrupts is the place to look to see if you might need it,
iff any of the devices of interest are shared.
my laptop shows sharing, my soekris does not

  3:          5          XT-PIC  ehci_hcd:usb1, ohci1394
  4:          0          XT-PIC  uhci_hcd:usb6
  7:     708975          XT-PIC  ipw2200, ehci_hcd:usb2, uhci_hcd:usb7
  8:          1          XT-PIC  rtc
  9:     437509          XT-PIC  acpi, Intel 82801DB-ICH4, Intel 
82801DB-ICH4 Modem, ohci_hcd:usb3, ohci_hcd:usb4, uhci_hcd:usb5, yenta, eth0

# cat /proc/interrupts
           CPU0
  0:   13148086          XT-PIC  timer
  2:          0          XT-PIC  cascade
  4:      33084          XT-PIC  serial
  8:          4          XT-PIC  rtc
 10:     337134          XT-PIC  eth0
 11:     926639          XT-PIC  ndiswrapper
 14:         11          XT-PIC  ide0
NMI:          0


XENO_OPT_SHIRQ_EDGE

does this only apply to ISA bus ?

XENO_SKIN_NATIVE

will add module name

XENO_OPT_NATIVE_INTR

Note that the preferred
way of implementing generic drivers usable across all Xenomai
interfaces is defined by the Real-Time Driver Model (RTDM).

It doesnt say theyre (in)?compatible, should it ?


SUMMARY

Id like to see estimates of the latency costs associated with each choice,
where its practical to do so (given the current unknowables, like 
variations across
cpus, chipsets etc).  I recognize that such numbers are the hoped-for
end result of the xenomai-data ML, and perhaps nothing real can be said
yet (or ever) in Kconfig, except in (overly?) broad statements.





             reply	other threads:[~2006-05-08  3:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-08  3:22 Jim Cromie [this message]
2006-05-08 16:37 ` [Xenomai-core] kconfig help questions Philippe Gerum

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=445EB95C.6050302@domain.hid \
    --to=jim.cromie@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.