All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: dm-devel@redhat.com, Srinivas Eeda <srinivas.eeda@oracle.com>,
	agk@redhat.com, "Martin K. Petersen" <martin.petersen@oracle.com>,
	"Darrick J. Wong" <darrick.wong@oracle.com>
Subject: Re: dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP
Date: Fri, 13 Feb 2015 16:12:24 -0500	[thread overview]
Message-ID: <yq1k2zlms7b.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20150213205858.GA7070@redhat.com> (Mike Snitzer's message of "Fri, 13 Feb 2015 15:58:58 -0500")

>>>>> "Mike" == Mike Snitzer <snitzer@redhat.com> writes:

Mike> Yeah, I'm OK with leaving it as is for now (allowing a mix).

That's fine with me as long as you're comfortable that we're handling
the corner cases correctly.

Mike> So I'll be picking your dm-io patch up for 3.20-rc.

Should also go to stable.

Mike> No, the DM table reload for Y would alter the discard capability
Mike> of Y but it will _not_ bubble up to X.

Mike> (would be nice if such limit stacking with refresh but...)

Yeah. We keep talking about this. Maybe we can have a quick brain storm
at LSF/MM?

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2015-02-13 21:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13  9:24 [PATCH] dm-io: reject unsupported DISCARD/WRITE SAME requests with EOPNOTSUPP Darrick J. Wong
2015-02-13 15:55 ` Mike Snitzer
2015-02-13 17:01   ` Darrick J. Wong
2015-02-13 19:21   ` Martin K. Petersen
2015-02-13 20:07     ` Darrick J. Wong
2015-02-13 20:58       ` Mike Snitzer
2015-02-13 21:12         ` Martin K. Petersen [this message]
2015-02-26 19:56   ` Mikulas Patocka
2015-02-26 20:10     ` Mikulas Patocka
2015-02-27 18:42     ` Darrick J. Wong

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=yq1k2zlms7b.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=agk@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=dm-devel@redhat.com \
    --cc=snitzer@redhat.com \
    --cc=srinivas.eeda@oracle.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.