From: Jens Axboe <axboe@suse.de>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Status of write barrier support for 2.4?
Date: Fri, 28 Jun 2002 20:20:53 +0200 [thread overview]
Message-ID: <20020628202053.C777@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.10.10206281108100.2888-100000@master.linux-ide.org>
On Fri, Jun 28 2002, Andre Hedrick wrote:
>
> Jens,
>
> I just got crapped all over trying to get us "write barrier" opcodes :-/.
> However I do have the start of a draft to submit soon. I could not piggy
> back of FUA by MicroSoft last week.
Basic FUA bit for WRITE command would be good, as long as it also
prevents reordering of the writes currently in write cache. I don't
think mmc makes any such guarentee, although I would have to check to be
sure.
> So how did the talk go at OLS for the IDE roadmap to destruction go?
> I could not attend, as I was doing other stuff associated with the
> industry.
I don't think there was such a talk?! If so, I didn't attend.
--
Jens Axboe
next prev parent reply other threads:[~2002-06-28 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-27 10:45 Matthias Andree
2002-06-28 18:02 ` Jens Axboe
2002-06-28 18:11 ` Andre Hedrick
2002-06-28 18:20 ` Jens Axboe [this message]
2002-06-28 18:21 ` Jens Axboe
2002-06-28 18:33 ` Andre Hedrick
2002-06-28 23:59 ` Matthias Andree
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=20020628202053.C777@suse.de \
--to=axboe@suse.de \
--cc=andre@linux-ide.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®