Re: Weird wasting of time between ioctl() and ioctl dispatcher

"Cestonaro, Thilo \(external\)"    <[email protected]> writes:

> I'm a developer for Fujitsu Siemens Computers, working on a program which has it's own kernel modules and userland components.
> Now cause the program should be released we have done some testing and during this testphase a wierd wasting of time occured
> during the call of the ioctl() in the userland component and the actuall entering of the dispatcher function in the module.
> It takes 3 min. until the call at last enters my dispatcher. 

Something else is holding the big kernel lock for that long. Most likely
it's your own code. Consider using a ->unlocked_ioctl

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Weird wasting of time between ioctl() and ioctl dispatcher
    • From: "Cestonaro, Thilo \(external\)" <[email protected]>

• Prev by Date: [patch] Re: 2.6.19-rc6-mm1 -- sched-improve-migration-accuracy.patch slows boot
• Next by Date: Re: [PATCH] paravirt reorder functions to avoid unspecified behaviour
• Previous by thread: Re: Weird wasting of time between ioctl() and ioctl dispatcher
• Next by thread: [PATCH 0/2] KVM: Sync with -mm tree
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]