All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Mike Snitzer <snitzer@redhat.com>,
	Ric Wheeler <rwheeler@redhat.com>,
	lsf-pc@lists.linuxfoundation.org, linux-fsdevel@vger.kernel.org,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [LSF/MM TOPIC] update on discard support & testing with vendors
Date: Mon, 17 Jan 2011 17:37:34 -0700	[thread overview]
Message-ID: <20110118003734.GE6262@parisc-linux.org> (raw)
In-Reply-To: <yq18vyjdrsh.fsf@sermon.lab.mkp.net>

On Mon, Jan 17, 2011 at 06:38:54PM -0500, Martin K. Petersen wrote:
> Yeah, many vendors stick to reporting compliance with really old
> revisions to prevent legacy operating systems from blowing up.

That sounds like a heuristic ... :-)

> However, the SCSI folks are vehemently against having heuristics in the
> first place (guess how many USB-ATA bridge vendors actively participate
> in T10).

It's an odd situation where 99.9% of the marketshare don't participate
in the standards committee.

> T10's official policy is that the device can fail any command
> with any (valid) arguments at any time. And that the OS stack should
> always retry with less data, try a different command variant, etc. That
> might be another good topic for discussion, actually. Because while we
> do have some hacks in place (use_10, etc.) things will soon get more
> complex.

I'd love to live in their world where the device won't fall over and
refuse to respond to any further commands without a power cycle.

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

      reply	other threads:[~2011-01-18  0:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-17 14:46 [LSF/MM TOPIC] update on discard support & testing with vendors Ric Wheeler
2011-01-17 23:18 ` Mike Snitzer
2011-01-17 23:38   ` Martin K. Petersen
2011-01-17 23:38     ` Martin K. Petersen
2011-01-18  0:37     ` Matthew Wilcox [this message]

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=20110118003734.GE6262@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=lsf-pc@lists.linuxfoundation.org \
    --cc=martin.petersen@oracle.com \
    --cc=rwheeler@redhat.com \
    --cc=snitzer@redhat.com \
    /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.