Exclusive control

Hi
I'm making a driver.
A tasklet is called from interrupt handler.
The driver supports read/write system call.

A tasklet and the read/write routines access the same resources.

In this case will exclusive control ,between tasklet and read/write,
be necessary?

Thanks!
tsuyoshi

.

Relevant Pages

  • Re: Exclusive control
    ... A tasklet and the read/write routines access the same resources. ...
    (comp.os.linux.development.system)
  • Re: USB high speed
    ... If you measured the performance by copy/paste files through UI, then there is a limitation on the payload size enforced by filesys (when filesys issues read/write operations down to storage driver level). ... >> Windows Devices Core BSPs ...
    (microsoft.public.windowsce.embedded)
  • driver hacking tips (was Re: [PATCH] QStor SATA/RAID driver for 2.6.9-rc3)
    ... Putting almost all your in-irq code into a tasklet can be quite ... does nothing but processes an internal driver event queue. ... event queue thread can sometimes be more simple than async work queue code. ...
    (Linux-Kernel)
  • Re: [PATCH] OMAP: Keypad driver
    ... I don't think the tasklet stopping code is correct. ... But the just-killed timer handler might have ... I will update the driver and submit the patch. ... May changelog needs URL entry like http://linux.omap.com _or_ ...
    (Linux-Kernel)
  • Re: Hooking IRPs
    ... even if you bypass filemon, i can set a bp on your driver's read/write ... Don Burn (MVP, Windows DDK) ... Windows 2k/XP/2k3 Filesystem and Driver Consulting ... but it seems that does not exist way to hide Read/Write ...
    (microsoft.public.development.device.drivers)