All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 2/7] qcow2: Discard/zero clusters by byte count
Date: Wed, 15 Feb 2017 16:46:42 +0100	[thread overview]
Message-ID: <20170215154642.GC4935@noname.redhat.com> (raw)
In-Reply-To: <20170214192525.18624-3-eblake@redhat.com>

Am 14.02.2017 um 20:25 hat Eric Blake geschrieben:
> Passing a byte offset, but sector count, when we ultimately
> want to operate on cluster granularity, is madness.  Clean up
> the external interfaces to take both offset and count as bytes,
> while still keeping the assertion added previously that the
> caller must align the values to a cluster.  Then rename things
> to make sure backports don't get confused by changed units:
> instead of qcow2_discard_clusters() and qcow2_zero_clusters(),
> we now have qcow2_cluster_discard() and qcow2_cluster_zeroize().
> 
> The internal functions still operate on clusters at a time, and
> return an int for number of cleared clusters; but on an image
> with 2M clusters, a single L2 table holds 256k entries that each
> represent a 2M cluster, totalling well over INT_MAX bytes if we
> ever had a request for that many bytes at once.  All our callers
> currently limit themselves to 32-bit bytes (and therefore fewer
> clusters), but by making this function 64-bit clean, we have one
> less place to clean up if we later improve the block layer to
> support 64-bit bytes through all operations (with the block layer
> auto-fragmenting on behalf of more-limited drivers), rather than
> the current state where some interfaces are artificially limited
> to INT_MAX at a time.
> 
> Signed-off-by: Eric Blake <eblake@redhat.com>

Reviewed-by: Kevin Wolf <kwolf@redhat.com>

  reply	other threads:[~2017-02-15 15:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-14 19:25 [Qemu-devel] [PATCH v5 0/7] add blkdebug tests Eric Blake
2017-02-14 19:25 ` [Qemu-devel] [PATCH v5 1/7] qcow2: Assert that cluster operations are aligned Eric Blake
2017-02-15 12:25   ` Kevin Wolf
2017-03-06 23:34     ` Eric Blake
2017-02-14 19:25 ` [Qemu-devel] [PATCH v5 2/7] qcow2: Discard/zero clusters by byte count Eric Blake
2017-02-15 15:46   ` Kevin Wolf [this message]
2017-02-14 19:25 ` [Qemu-devel] [PATCH v5 3/7] blkdebug: Sanity check block layer guarantees Eric Blake
2017-02-14 19:25 ` [Qemu-devel] [PATCH v5 4/7] blkdebug: Add pass-through write_zero and discard support Eric Blake
2017-02-15 15:53   ` Kevin Wolf
2017-02-14 19:25 ` [Qemu-devel] [PATCH v5 5/7] blkdebug: Simplify override logic Eric Blake
2017-02-15 15:58   ` Kevin Wolf
2017-02-14 19:25 ` [Qemu-devel] [PATCH v5 6/7] blkdebug: Add ability to override unmap geometries Eric Blake
2017-02-15 16:20   ` Kevin Wolf
2017-03-07 21:14     ` Eric Blake
2017-02-14 19:25 ` [Qemu-devel] [PATCH v5 7/7] tests: Add coverage for recent block geometry fixes Eric Blake

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=20170215154642.GC4935@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=eblake@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.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 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.