Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: willy@linux.intel.com (Matthew Wilcox)
Subject: Cmd - comp write
Date: Thu, 24 Apr 2014 09:58:05 -0400	[thread overview]
Message-ID: <20140424135805.GA5886@linux.intel.com> (raw)
In-Reply-To: <7212DDF9-6821-4D7E-BD4D-655031AD03F7@gmail.com>

On Wed, Apr 23, 2014@08:37:39PM -0700, Learner wrote:
> Hello
> 
> How frequently is Fused command - compare-write used? 
> Is it for avoiding writes for SSDs if thee is no change? Ie read and compare the block to be written and don't write if there is no change.. 

Compare-and-Write is a building block for an (unspecified, advisory)
locking protocol.  If two entities wish to gain exclusive access to a
range of LBAs, they can agree on a block to use as their lock, and agree
on a bit-pattern to be found in that block to indicate 'unlocked'.

If anyone is using it, they're doing so through ioctls; there's no way
to submit a BIO that maps to a compare-and-write.

  parent reply	other threads:[~2014-04-24 13:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24  3:37 Cmd - comp write Learner
2014-04-24  9:50 ` Ebrahim Hashemi
2014-04-24 13:58 ` Matthew Wilcox [this message]
2014-04-24 17:03   ` Learner Study
2014-04-24 17:43     ` Matthew Wilcox

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=20140424135805.GA5886@linux.intel.com \
    --to=willy@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox