Linux Device Mapper development
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Jens Axboe <jaxboe@fusionio.com>,
	device-mapper development <dm-devel@redhat.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Zdenek Kabelac <zkabelac@redhat.com>
Subject: Re: [PATCH] block: Require subsystems to explicitly allocate bio_set integrity mempool
Date: Fri, 11 Mar 2011 12:11:55 -0500	[thread overview]
Message-ID: <yq1lj0l60pw.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20110311165305.GA28769@redhat.com> (Mike Snitzer's message of "Fri, 11 Mar 2011 11:53:05 -0500")

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

>> Yeah, that'll come as part of my DIX1.1 patch set.

Mike> Seems my concern should be fixed independent of a larger update
Mike> patchset.  Unless DIX isn't meaningful for "stable" kernels
Mike> without your full DIX1.1 update?

Well, I'm not aware of any shipping non-512 byte block DIF devices other
than scsi_debug.

And it's not good enough to just fix it in DM since this is a hardware
parameter that needs to be queried and bubbled up. It can't be scaled
like the rest of the topology block sizes, it's wired in the
hardware. So I just don't see much point in trying to fix it now when
any ties to the logical block size will be severed in my impending patch
set.

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2011-03-11 17:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-28 11:21 mirrored device with thousand of mapping table entries Eli Malul
2011-02-28 11:48 ` Alasdair G Kergon
2011-02-28 11:59   ` mirrored device with thousand of mapping tableentries Eli Malul
2011-02-28 12:11     ` Alasdair G Kergon
2011-02-28 12:17       ` mirrored device with thousand of mappingtableentries Eli Malul
2011-02-28 13:10         ` Alasdair G Kergon
2011-02-28 13:13           ` Eli Malul
2011-02-28 13:29             ` Alasdair G Kergon
2011-02-28 13:42               ` Eli Malul
2011-02-28 16:25               ` Eli Malul
2011-02-28 13:38             ` Zdenek Kabelac
2011-02-28 15:01               ` Martin K. Petersen
2011-03-06 20:39                 ` Zdenek Kabelac
2011-03-07  2:59                   ` Martin K. Petersen
2011-03-07 14:24                     ` Zdenek Kabelac
2011-03-07 16:09                     ` Mike Snitzer
2011-03-08  6:51                       ` Martin K. Petersen
2011-03-08 17:13                         ` Mike Snitzer
2011-03-10 16:11                           ` Martin K. Petersen
2011-03-11 16:53                             ` [PATCH] block: Require subsystems to explicitly allocate bio_set integrity mempool (was: Re: mirrored device with thousand of mappingtableentries) Mike Snitzer
2011-03-11 17:11                               ` Martin K. Petersen [this message]
2011-03-07 20:10                     ` mirrored device with thousand of mappingtableentries Mike Snitzer
2011-03-07 20:22                       ` Martin K. Petersen

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=yq1lj0l60pw.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=dm-devel@redhat.com \
    --cc=jaxboe@fusionio.com \
    --cc=snitzer@redhat.com \
    --cc=zkabelac@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox