From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Sam Bradshaw (sbradshaw)" <sbradshaw@micron.com>
Subject: Re: [GIT PULL] Block drivers for 3.3-rc
Date: Sun, 15 Jan 2012 07:44:05 -0500 [thread overview]
Message-ID: <20120115124405.GA7389@infradead.org> (raw)
In-Reply-To: <4F12C4ED.6060301@kernel.dk>
On Sun, Jan 15, 2012 at 01:22:05PM +0100, Jens Axboe wrote:
> Good point, I had forgotten about the ordered writes, I believe the rest
> of the items have been handled. The driver/hw, as it stands, does not
> reorder writes and it doesn't have a write back cache. So it should
> actually be safe. Any acked write is stable. Sam, correct me if I'm
> wrong.
I tried to get that out of the micron folks a while ago but don't
remember getting an answer. If that's actually tree please remove
the (misnamed) barrier argument from mtip_hw_submit_io, and maybe add
a comment that the current hardware can't have a volatile write cache.
Btw, does the hardware claim to have writeback caches in the ATA
IDENTIFY words related to it?
next prev parent reply other threads:[~2012-01-15 12:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 9:52 [GIT PULL] Block drivers for 3.3-rc Jens Axboe
2012-01-15 10:33 ` Christoph Hellwig
2012-01-15 12:22 ` Jens Axboe
2012-01-15 12:44 ` Christoph Hellwig [this message]
2012-01-15 12:50 ` Jens Axboe
2012-01-16 19:10 ` Sam Bradshaw (sbradshaw)
2012-01-16 19:13 ` Sam Bradshaw (sbradshaw)
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=20120115124405.GA7389@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=sbradshaw@micron.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.