netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan-Bernd Themann <ossthema@de.ibm.com>
To: Anton Blanchard <anton@samba.org>
Cc: themann@de.ibm.com, netdev@vger.kernel.org
Subject: Re: ehea work queues
Date: Mon, 1 Oct 2007 16:43:04 +0200	[thread overview]
Message-ID: <200710011643.04180.ossthema@de.ibm.com> (raw)
In-Reply-To: <20070930162019.GE28619@kryten>

Hi

On Sunday 30 September 2007 18:20, Anton Blanchard wrote:
> 
> Hi,
> 
> I booted 2.6.23-rc8 and noticed that ehea loves its workqueues:
> (notice also that the ehea_driver_wq/XXX exceeds TASK_COMM_LEN). 
> 
> Since they are both infrequent events and not performance critical
> (memory hotplug and driver reset), can we just use schedule_work?
> 
Yes. I'll provide a patch soon.

Thanks,
Jan-Bernd

      reply	other threads:[~2007-10-01 14:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-30 16:20 ehea work queues Anton Blanchard
2007-10-01 14:43 ` Jan-Bernd Themann [this message]

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=200710011643.04180.ossthema@de.ibm.com \
    --to=ossthema@de.ibm.com \
    --cc=anton@samba.org \
    --cc=netdev@vger.kernel.org \
    --cc=themann@de.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).