linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Theodore Ts'o <tytso@mit.edu>,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
	sfr@canb.auug.org.au
Subject: Re: [GIT PULL] ext4 update for 2.6.39-rc1
Date: Fri, 25 Mar 2011 18:24:46 +0100	[thread overview]
Message-ID: <20110325172446.GH1409@htj.dyndns.org> (raw)
In-Reply-To: <AANLkTi=aKLhtuuMtd=KZ8YBykCp=yJ-KPAJ3jKQq0jQW@mail.gmail.com>

Hello, Linus.

On Fri, Mar 25, 2011 at 10:02:48AM -0700, Linus Torvalds wrote:
> Ok, guys, can you verify my merge? In one branch, we had Tejun change
> it to use "alloc_workqueue()", and in another, ext4 switched from
> create_workqueue() to create_singlethread_workqueue().
> 
> My resolution was to use WQ_UNBOUND in allow_workqueue() in the
> resulting merge, which I think should be semantically the correct
> resolve. But the commit message in the create_singlethread_workqueue()
> change seems to imply that the single-threadedness isn't a
> _correctness_ issue as much as it is just a "we don't need multiple
> threads" issue, so maybe the WQ_UNBOUND isn't necessary. So WQ_UNBOUND
> may or may not be a good idea.
> 
> Regardless, please give it a look, ok?

The merg should be safe but WQ_UNBOUND isn't necessary there, so I
think the version from commit fd89d5f2030a ("ext4: convert to
alloc_workqueue()") would be better.  BTW, Stephen already spotted
this earlier today - https://lkml.org/lkml/2011/3/24/652

Thanks.

-- 
tejun

      reply	other threads:[~2011-03-25 17:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-25  2:32 [GIT PULL] ext4 update for 2.6.39-rc1 Theodore Ts'o
2011-03-25 17:02 ` Linus Torvalds
2011-03-25 17:24   ` Tejun Heo [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=20110325172446.GH1409@htj.dyndns.org \
    --to=tj@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /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).