added num_pieces to peer_info. Fixes #385

This commit is contained in:
Arvid Norberg
2008-10-24 00:15:39 +00:00
parent f7b22e3517
commit 971f437b41
4 changed files with 11 additions and 0 deletions

View File

@@ -2749,6 +2749,8 @@ struct peer_info
int rtt; int rtt;
int num_pieces;
int download_rate_peak; int download_rate_peak;
int upload_rate_peak; int upload_rate_peak;
@@ -2968,6 +2970,7 @@ assigned to be allowed to send and receive until it has to request more quota
from the bandwidth manager.</p> from the bandwidth manager.</p>
<p><tt class="docutils literal"><span class="pre">rtt</span></tt> is an estimated round trip time to this peer, in milliseconds. It is <p><tt class="docutils literal"><span class="pre">rtt</span></tt> is an estimated round trip time to this peer, in milliseconds. It is
estimated by timing the the tcp <tt class="docutils literal"><span class="pre">connect()</span></tt>. It may be 0 for incoming connections.</p> estimated by timing the the tcp <tt class="docutils literal"><span class="pre">connect()</span></tt>. It may be 0 for incoming connections.</p>
<p><tt class="docutils literal"><span class="pre">num_pieces</span></tt> is the number of pieces this peer has.</p>
<p><tt class="docutils literal"><span class="pre">download_rate_peak</span></tt> and <tt class="docutils literal"><span class="pre">upload_rate_peak</span></tt> are the highest download and upload <p><tt class="docutils literal"><span class="pre">download_rate_peak</span></tt> and <tt class="docutils literal"><span class="pre">upload_rate_peak</span></tt> are the highest download and upload
rates seen on this connection. They are given in bytes per second. This number is rates seen on this connection. They are given in bytes per second. This number is
reset to 0 on reconnect.</p> reset to 0 on reconnect.</p>

View File

@@ -2708,6 +2708,8 @@ It contains the following fields::
int rtt; int rtt;
int num_pieces;
int download_rate_peak; int download_rate_peak;
int upload_rate_peak; int upload_rate_peak;
@@ -2927,6 +2929,8 @@ from the bandwidth manager.
``rtt`` is an estimated round trip time to this peer, in milliseconds. It is ``rtt`` is an estimated round trip time to this peer, in milliseconds. It is
estimated by timing the the tcp ``connect()``. It may be 0 for incoming connections. estimated by timing the the tcp ``connect()``. It may be 0 for incoming connections.
``num_pieces`` is the number of pieces this peer has.
``download_rate_peak`` and ``upload_rate_peak`` are the highest download and upload ``download_rate_peak`` and ``upload_rate_peak`` are the highest download and upload
rates seen on this connection. They are given in bytes per second. This number is rates seen on this connection. They are given in bytes per second. This number is
reset to 0 on reconnect. reset to 0 on reconnect.

View File

@@ -193,6 +193,9 @@ namespace libtorrent
// estimated rtt to peer, in milliseconds // estimated rtt to peer, in milliseconds
int rtt; int rtt;
// the number of pieces this peer has
int num_pieces;
// the highest transfer rates seen for this peer // the highest transfer rates seen for this peer
int download_rate_peak; int download_rate_peak;
int upload_rate_peak; int upload_rate_peak;

View File

@@ -2593,6 +2593,7 @@ namespace libtorrent
p.pending_disk_bytes = m_outstanding_writing_bytes; p.pending_disk_bytes = m_outstanding_writing_bytes;
p.send_quota = m_bandwidth_limit[upload_channel].quota_left(); p.send_quota = m_bandwidth_limit[upload_channel].quota_left();
p.receive_quota = m_bandwidth_limit[download_channel].quota_left(); p.receive_quota = m_bandwidth_limit[download_channel].quota_left();
p.num_pieces = m_num_pieces;
if (m_download_queue.empty()) p.request_timeout = -1; if (m_download_queue.empty()) p.request_timeout = -1;
else p.request_timeout = total_seconds(m_requested - now) + m_ses.settings().request_timeout else p.request_timeout = total_seconds(m_requested - now) + m_ses.settings().request_timeout
+ m_timeout_extend; + m_timeout_extend;