mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andre Hedrick <andre@linux-ide.org>
To: Jens Axboe <axboe@suse.de>
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 11:11:00 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.10206281108100.2888-100000@master.linux-ide.org> (raw)
In-Reply-To: <20020628200203.A777@suse.de>


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.

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.

Cheers,

Andre Hedrick
LAD Storage Consulting Group

On Fri, 28 Jun 2002, Jens Axboe wrote:

> On Thu, Jun 27 2002, Matthias Andree wrote:
> > Hi,
> > 
> > what is the status of write barrier support in Linux?
> 
> We have stable support for IDE (ie block layer barrier support works,
> IDE implementation works). I doubt we'll ever do 2.4 SCSI support,
> it would be too invasive to really make it safe.
> 
> > Is there a web page that documents patches and status?
> 
> Not to my knowledge.
> 
> -- 
> Jens Axboe
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


  reply	other threads:[~2002-06-28 18:08 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 [this message]
2002-06-28 18:20     ` Jens Axboe
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=Pine.LNX.4.10.10206281108100.2888-100000@master.linux-ide.org \
    --to=andre@linux-ide.org \
    --cc=axboe@suse.de \
    --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®