From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Par-Gunnar Hjalmdahl <pghatwork@gmail.com>
Cc: linus.walleij@stericsson.com, linux-bluetooth@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/9] mfd: Add UART support for the ST-Ericsson CG2900.
Date: Fri, 29 Oct 2010 17:24:43 +0100 [thread overview]
Message-ID: <20101029172443.61f7b067@pyx> (raw)
In-Reply-To: <AANLkTinj93zAXJAipB3HjE62Xa1Z=9k9gPBxaT=+MLtg@mail.gmail.com>
> The reason is that the work is generated so often that a work is not
> finished before next work of same type comes. This is especially true
> for transmit and receive. Then I get 0 back when queuing the work and
> there is no real way to solve it from what I can see than to allocate
> new work structures every time.
So if that is the case what bounds your memory usage - can a busy box end
up with thousands of work queue slos used ? It sounds like your model is
perhaps wrong - if there is a continual stream of work maybe you should
simply have a kernel thread to handle it if it cannot be deferred
- remember ldisc code is able to sleep in most paths.
next prev parent reply other threads:[~2010-10-29 16:24 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 10:38 [PATCH 5/9] mfd: Add UART support for the ST-Ericsson CG2900 Par-Gunnar Hjalmdahl
2010-10-22 12:51 ` Alan Cox
2010-10-22 14:54 ` Par-Gunnar Hjalmdahl
2010-10-22 15:33 ` Alan Cox
2010-10-28 10:37 ` Par-Gunnar Hjalmdahl
2010-10-28 12:22 ` Arnd Bergmann
2010-10-29 11:58 ` Par-Gunnar Hjalmdahl
2010-10-29 12:08 ` Par-Gunnar Hjalmdahl
2010-10-30 0:09 ` Arnd Bergmann
2010-10-29 16:22 ` Alan Cox
2010-10-30 0:01 ` Arnd Bergmann
2010-10-31 12:04 ` Alan Cox
2010-11-05 17:02 ` Par-Gunnar Hjalmdahl
2010-11-05 17:19 ` Alan Cox
2010-11-08 5:24 ` Arnd Bergmann
2010-11-11 14:28 ` Par-Gunnar Hjalmdahl
2010-11-11 14:40 ` Par-Gunnar Hjalmdahl
2010-11-11 15:12 ` Arnd Bergmann
2010-10-29 11:53 ` Par-Gunnar Hjalmdahl
2010-10-29 16:24 ` Alan Cox [this message]
2010-12-03 9:16 ` Par-Gunnar Hjalmdahl
2010-12-03 11:42 ` Vitaly Wool
2010-12-03 11:42 ` Vitaly Wool
2010-12-06 9:06 ` Par-Gunnar Hjalmdahl
2010-12-06 9:06 ` Par-Gunnar Hjalmdahl
2010-12-06 9:46 ` Vitaly Wool
2010-12-06 12:01 ` Par-Gunnar Hjalmdahl
2010-12-06 12:01 ` Par-Gunnar Hjalmdahl
2010-12-06 12:25 ` Vitaly Wool
2010-12-06 14:49 ` Arnd Bergmann
2010-12-06 14:57 ` Vitaly Wool
2010-12-06 14:06 ` Arnd Bergmann
2010-12-06 14:54 ` Vitaly Wool
2010-12-06 15:15 ` Arnd Bergmann
2010-12-06 15:28 ` Vitaly Wool
2010-12-06 16:54 ` Arnd Bergmann
2010-12-06 21:24 ` Vitaly Wool
2010-12-06 23:07 ` Arnd Bergmann
2010-12-08 7:41 ` Pavan Savoy
2010-12-08 7:41 ` Pavan Savoy
2010-12-08 12:21 ` Par-Gunnar Hjalmdahl
2010-12-08 12:21 ` Par-Gunnar Hjalmdahl
2010-12-08 12:51 ` Arnd Bergmann
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=20101029172443.61f7b067@pyx \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linus.walleij@stericsson.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pghatwork@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.