Re: locking in a device driver

From: Dinesh Nair (dinesh_at_alphaque.com)
Date: 10/28/05

  • Next message: Mark Kirkwood: "Display files currently in the buffer cache"
    Date: Fri, 28 Oct 2005 21:58:42 +0800
    To: Scott Long <scottl@samsco.org>
    
    

    On 10/27/05 22:00 Scott Long said the following:
    > If you need to protect your pseudodriver from being interrupted by the
    > real driver then you'll need to use the same spl() as the driver. Note
    > that you shouldn't be using splhigh() unless you really know what you

    the driver currently is set to use INTR_TYPE_MISC, which from my
    understanding can only be masked with splhigh(). using another INTR_TYPE
    may be possible, so this is something i can explore.

    however, the device interrupts at a constant 1000Hz, as it's a quad-span
    E1/T1 line card, and thus it needs to have that interrupt serviced pronto
    to avoid E1/T1 frame slips. any advice here ?

    -- 
    Regards,                           /\_/\   "All dogs go to heaven."
    dinesh@alphaque.com                (0 0)    http://www.alphaque.com/
    +==========================----oOO--(_)--OOo----==========================+
    | for a in past present future; do                                        |
    |   for b in clients employers associates relatives neighbours pets; do   |
    |   echo "The opinions here in no way reflect the opinions of my $a $b."  |
    | done; done                                                              |
    +=========================================================================+
    _______________________________________________
    freebsd-hackers@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
    To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
    

  • Next message: Mark Kirkwood: "Display files currently in the buffer cache"

    Relevant Pages

    • Re: High resolution timer on kernel mode
      ... The problem I have is that this driver is ... interrupts then do your work in the interrupt handler ... ... timer all of the time ... ... So for me if the packets are coming in very slowly ... ...
      (microsoft.public.development.device.drivers)
    • [RFC/PATCH] Kdump: Disabling PCI interrupts in capture kernel
      ... In kdump, sometimes, general driver initialization issues seems to be cropping ... devices are sending interrupts while second kernel is booting and drivers are ... not expecting any interrupts yet. ... we need something generic which disables interrupt generation from device ...
      (Linux-Kernel)
    • Re: Handling PCI interrupts
      ... That makes sense but it also means the 'software interrupts' only occur on ... Your driver will probably be in a stack of its own. ... The DSP has standard PCI interrupts, but in addition ... driver by flipping bits in a separate register. ...
      (microsoft.public.development.device.drivers)
    • [PATCH 2.6.16] Shared interrupts sometimes lost
      ... wireless cards - based on the RaLink 2560 chip set. ... This is using the "legacy" rt2500 driver derived from the vendor ... But Linux is definitely implicated in the loss of interrupts. ... This is my first real introduction to the IRQ handling code in Linux, ...
      (Linux-Kernel)
    • Re: Polling for ath driver
      ... TCP) livelock is not really an issue, as the the streams will slow their ... These are tradeoffs that one accepts when using polling. ... The interrupts are the RX and TX interrupts. ... ethernet driver, the hifn crypto card driver, and the ath driver. ...
      (freebsd-net)