linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Peter Chang <dpf@google.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: PATCH: platforms: avoid queuing work if possible
Date: Fri, 31 Jan 2014 06:53:40 -0500	[thread overview]
Message-ID: <20140131115340.GD26148@htj.dyndns.org> (raw)
In-Reply-To: <CAF2xp_HgT+2zmxHTYpxRFiK-pfQKQJhJ74SJhQVER4s2ZZX0PQ@mail.gmail.com>

Hello,

On Thu, Jan 30, 2014 at 05:24:16PM -0800, Peter Chang wrote:
> 774a1221e862b343388347bac9b318767336b20b tries to avoid an expensive sync
> by marking the current task iff it uses the async_schedule() machinery.

That wasn't an optimization.  It was a workaround for deadlock.

> however, if the part of the driver's probe is called through a worker
> thread the bookeeping fails to mark the correct task as having used the
> async machinery.
> 
> this is a workaround for the common case that we're already running
> on the correct cpu. however, it seems sort of reasonable to not use
> the worker thread if we don't have to.
> 
> Tested:
> - checked on vebmy2 (ibis + satasquatch) which is where the original issue
>   was discovered.
> - checked on fdha347 (ikaria + loggerhead + satasquatch) to show that
>   nothing changed.

The patch description doesn't describe the reasons for the change at
all.  What issues have you encountered?  What are you trying to
achieve?

> Change-Id: Ibe8996cf652735c74a9e06ba9fd03118078395bd
> Google-Bug-Id: 12632867

The above tags don't mean anything upstream.  Please drop them when
posting patches.

Thanks.

-- 
tejun

  reply	other threads:[~2014-01-31 11:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-31  1:24 PATCH: platforms: avoid queuing work if possible Peter Chang
2014-01-31 11:53 ` Tejun Heo [this message]
2014-01-31 12:00   ` Tejun Heo
2014-02-05  4:13   ` Peter Chang
2014-02-10 22:41     ` Tejun Heo

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=20140131115340.GD26148@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=dpf@google.com \
    --cc=linux-pci@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;
as well as URLs for NNTP newsgroup(s).