From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: agraf@suse.de, qemu-devel@nongnu.org, armbru@redhat.com
Subject: [Qemu-devel] Re: [PATCH] Make strtosz() return int64_t instead of ssize_t
Date: Wed, 05 Jan 2011 20:30:43 +0100 [thread overview]
Message-ID: <4D24C6E3.5040205@redhat.com> (raw)
In-Reply-To: <4D24B8A1.9060801@codemonkey.ws>
On 01/05/11 19:29, Anthony Liguori wrote:
> I wouldn't make such bold claims but I'll concede that one is not
> significantly better than the other and won't object to int64_t if you
> feel strongly.
The more I think of it, the more I come to the conclusion that int64_t
is the best solution. Since we can in theory have a system where we only
allow 32 bit file system offsets, but have > 4GB of memory, int64_t does
it best - it is more generic.
Cheers,
Jes
next prev parent reply other threads:[~2011-01-05 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 10:41 [Qemu-devel] [PATCH] Make strtosz() return int64_t instead of ssize_t Jes.Sorensen
2011-01-05 12:34 ` [Qemu-devel] " Michael S. Tsirkin
2011-01-05 12:36 ` Jes Sorensen
2011-01-05 12:49 ` Michael S. Tsirkin
2011-01-05 13:46 ` Anthony Liguori
2011-01-05 14:40 ` Jes Sorensen
2011-01-05 18:29 ` Anthony Liguori
2011-01-05 19:30 ` Jes Sorensen [this message]
2011-01-11 13:36 ` [Qemu-devel] " Kevin Wolf
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=4D24C6E3.5040205@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).