mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Franck <vagabon.xyz@gmail.com>
To: linux-usb-devel@lists.sourceforge.net,
	lkml <linux-kernel@vger.kernel.org>
Subject: kernel is overwhelmed by usb hcd's interrupts
Date: Fri, 21 Oct 2005 16:02:40 +0200	[thread overview]
Message-ID: <cda58cb80510210702g3b0c0bdbk@mail.gmail.com> (raw)

Hi,

I've written an usb driver for linux for a specific usb host
controler. Basicaly the hw generates an interrupt every 1 ms (every
start of frame) and during transfers interrupts can be generated every
30 us ! My cpu is a MIPS one running at 96Mhz and HZ is 100.

After transfering 20M bytes of data through USB, the kernel loops for
a while in timer interrupt handler. It actually loops in update_times
with tick (jiffies - wall_jiffies) value equals to 3707637046 ! I
guess that the kernel have lost a lot of timer ticks...However
interrupts are enable inside usb driver, I don't see how the kernel
can lost so many ticks.

Could anyone give me some advices for that ?

Thanks
--
               Franck

                 reply	other threads:[~2005-10-21 14:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=cda58cb80510210702g3b0c0bdbk@mail.gmail.com \
    --to=vagabon.xyz@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome