public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: mike <mikelee@avantwave.com>
To: Linux kernel mailing <linux-kernel@vger.kernel.org>
Subject: About Tasklet scheduling
Date: Mon, 08 Nov 2004 15:19:07 +0800	[thread overview]
Message-ID: <418F1DEB.7000905@avantwave.com> (raw)

Dear all

    I am new to kernel driver development. Thanks for any help.

    I am modifing a USB Ramdisk to a USB mass storage(MTD) driver in a 
dragonball ARM9 platform.  I stop when using tasklet. The USB driver 
setup with endpoint 1 and 2 to be Interrupt IN and OUT point. So when 
ever there is a interrupt , I schedule the tasklet to read or write with 
semphone variable protection.
    The problem i am facing is that the read/write process is TOO SLOW 
for the host to response. I have tried to not use tasklet and call the 
read/write function directly, it works with small file but "schedule in 
interrupt" oops prompt out when transfer a large file . I have also try 
to use spin_lock_irqsave.. but it will stop the interrupt...

    I am in a hurry on this. Please give me a hand.

    Thanks

Mike,Lee

                 reply	other threads:[~2004-11-08  7:13 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=418F1DEB.7000905@avantwave.com \
    --to=mikelee@avantwave.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox