From: John Snow <jsnow@redhat.com>
To: ali saeedi <ali.saeedi56@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] bytes xfer
Date: Mon, 1 May 2017 12:00:24 -0400 [thread overview]
Message-ID: <464e19e7-a11e-fc28-a6ed-b6f1506658be@redhat.com> (raw)
In-Reply-To: <CAGKXQyewQkpv=KgCYt86VAvrPmFdsQvs3kev_W74OrJApUvfEg@mail.gmail.com>
On 04/29/2017 01:23 AM, ali saeedi wrote:
> Hi
> what does 'bytes_xfer' and 'xfer_limit' mean?
> I am new in qemu.
> thanks a lot
>
The exact meaning is going to change depending on where you are looking.
As advice for mailing a technical list, please be prepared with code
excerpts from the files you are investigating and provide filenames and
line numbers so that your question can be answered.
As for your question:
'bytes_xfer' is likely short for "Bytes Transferred" and counts the
number of bytes sent over a socket or stream.
'xfer_limit' is likely short for "Transfer Limit" and counts either a
total or per-time-slice count of how many bytes can be transferred
before we hit some kind of quota, to avoid saturating resources.
--js
prev parent reply other threads:[~2017-05-01 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-29 5:23 [Qemu-devel] bytes xfer ali saeedi
2017-05-01 16:00 ` John Snow [this message]
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=464e19e7-a11e-fc28-a6ed-b6f1506658be@redhat.com \
--to=jsnow@redhat.com \
--cc=ali.saeedi56@gmail.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).