From: Theodore Ts'o <tytso@mit.edu>
To: Lukas Czerner <lczerner@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH 3/3] ext4: Do no use yield() in ext4 code
Date: Sun, 10 Mar 2013 22:41:07 -0400 [thread overview]
Message-ID: <20130311024107.GH10090@thunk.org> (raw)
In-Reply-To: <1362730998-3263-3-git-send-email-lczerner@redhat.com>
On Fri, Mar 08, 2013 at 09:23:18AM +0100, Lukas Czerner wrote:
> Using yield() is strongly discouraged (see sched/core.c) especially
> since we can just use cond_resched().
>
> Replace all use of yield() with cond_resched().
>
> Signed-off-by: Lukas Czerner <lczerner@redhat.com>
Thanks, applied.
- Ted
next prev parent reply other threads:[~2013-03-11 2:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 8:23 [PATCH 1/3] ext4: remove unused variable in ext4_free_blocks() Lukas Czerner
2013-03-08 8:23 ` [PATCH 2/3] ext4: Use kstrtoul() instead of deprecated simple_strtoul() Lukas Czerner
2013-03-11 2:26 ` Theodore Ts'o
2013-03-11 7:36 ` Lukáš Czerner
2013-03-11 15:38 ` Theodore Ts'o
2013-03-08 8:23 ` [PATCH 3/3] ext4: Do no use yield() in ext4 code Lukas Czerner
2013-03-11 2:41 ` Theodore Ts'o [this message]
2013-03-11 2:25 ` [PATCH 1/3] ext4: remove unused variable in ext4_free_blocks() Theodore Ts'o
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=20130311024107.GH10090@thunk.org \
--to=tytso@mit.edu \
--cc=lczerner@redhat.com \
--cc=linux-ext4@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).