All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Peter Lieven <pl@kamp.de>, Charles Arnold <carnold@suse.com>
Cc: Kevin Wolf <kwolf@redhat.com>, Jeff Cody <jcody@redhat.com>,
	"<qemu-devel@nongnu.org>" <qemu-devel@nongnu.org>,
	"<stefanha@redhat.com>" <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH] vpc: Ignore geometry for large images
Date: Wed, 18 Feb 2015 07:11:54 -0700	[thread overview]
Message-ID: <54E49DAA.5010003@redhat.com> (raw)
In-Reply-To: <54E495D3.80900@kamp.de>

[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]

[meta-comment]

On 02/18/2015 06:38 AM, Peter Lieven wrote:

>>>>>>>>>>>>>>>> Am 09.02.2015 um 17:09 schrieb Kevin Wolf:
>>>>>>>>>>>>>>>>> The CHS calculation as done per the VHD spec imposes a maximum

That's a LOT of nested quoting.  It's okay to trim your reply to cut out
the portion of the thread that people have already seen 17 times. :)

>> Right, although this was a long time ago for me to remember the specifics :)
>> In the end I think supporting at least the 2 TB size allowed by the spec is what
>> we need while not breaking existing images.
> 
> Thats clear, the absolute limit is 2 TB. We still refuse large images with -EFBIG.
> Before your patch every image above 127GB was refused with that error.

For example, trimming to just this much means that the reply occurs on
the first screenful, rather than having to scroll through several pages
of quotes to find new content.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2015-02-18 14:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-09 16:09 [Qemu-devel] [RFC PATCH] vpc: Ignore geometry for large images Kevin Wolf
2015-02-10 11:41 ` Peter Lieven
2015-02-10 13:34   ` Kevin Wolf
2015-02-10 13:42     ` Jeff Cody
2015-02-10 13:54       ` Kevin Wolf
2015-02-10 14:00         ` Peter Lieven
2015-02-10 14:53           ` Kevin Wolf
2015-02-12  9:23             ` Peter Lieven
2015-02-12  9:58               ` Kevin Wolf
2015-02-12 10:02                 ` Peter Lieven
2015-02-12 10:06                   ` Kevin Wolf
2015-02-12 10:09                     ` Peter Lieven
2015-02-12 10:23                       ` Kevin Wolf
2015-02-12 10:30                         ` Peter Lieven
2015-02-12 17:18                         ` Charles Arnold
2015-02-12 19:05                           ` Peter Lieven
2015-02-12 21:01                             ` Charles Arnold
2015-02-18 13:38                               ` Peter Lieven
2015-02-18 14:11                                 ` Eric Blake [this message]
2015-02-10 14:11         ` Jeff Cody

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=54E49DAA.5010003@redhat.com \
    --to=eblake@redhat.com \
    --cc=carnold@suse.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pl@kamp.de \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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.