From: Jens Axboe <jens.axboe@oracle.com>
To: Nick Piggin <npiggin@suse.de>
Cc: linux-scsi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [rfc][patch 1/3] block: non-atomic queue_flags prep
Date: Tue, 18 Dec 2007 08:44:40 +0100 [thread overview]
Message-ID: <20071218074439.GB31964@kernel.dk> (raw)
In-Reply-To: <20071215054315.GA30335@wotan.suse.de>
On Sat, Dec 15 2007, Nick Piggin wrote:
> Hi,
>
> This is just an idea I had, which might make request processing a little
> bit cheaper depending on queue behaviour. For example if it is getting plugged
> unplugged frequently (as I think is the case for some database workloads),
> then we might save one or two atomic operations per request.
>
> Anyway, I'm not completely sure if I have ensured all queue_flags users are
> safe (I think md may need a bit of help). But overall it seems quite doable.
Looks ok to me, I'll throw it into the testing mix. Thanks Nick!
--
Jens Axboe
next prev parent reply other threads:[~2007-12-18 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 5:43 [rfc][patch 1/3] block: non-atomic queue_flags prep Nick Piggin
2007-12-15 5:43 ` [rfc][patch 2/3] block: non-atomic queue_flags Nick Piggin
2007-12-15 5:44 ` [rfc][patch 3/3] block: non-atomic queue_flags accessors Nick Piggin
2007-12-18 7:44 ` Jens Axboe [this message]
2007-12-18 8:13 ` [rfc][patch 1/3] block: non-atomic queue_flags prep Nick Piggin
2007-12-19 18:13 ` Jens Axboe
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=20071218074439.GB31964@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=npiggin@suse.de \
/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).