Re: [ppsp] [Spam] 回复: Re:回复: Re: Proposal to resolve Issue 10 + 13

Arno Bakker <arno@cs.vu.nl> Wed, 09 May 2012 06:18 UTC

Return-Path: <a.bakker@vu.nl>
X-Original-To: ppsp@ietfa.amsl.com
Delivered-To: ppsp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43AAE21F85D4 for <ppsp@ietfa.amsl.com>; Tue, 8 May 2012 23:18:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.581
X-Spam-Level: ****
X-Spam-Status: No, score=4.581 tagged_above=-999 required=5 tests=[AWL=-3.810, BAYES_50=0.001, CHARSET_FARAWAY_HEADER=3.2, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_LOW=-1, SARE_SUB_ENC_GB2312=1.345]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m-BpVQB2Yopo for <ppsp@ietfa.amsl.com>; Tue, 8 May 2012 23:18:47 -0700 (PDT)
Received: from mailin.vu.nl (mailin.vu.nl [130.37.164.19]) by ietfa.amsl.com (Postfix) with ESMTP id 2E1B121F85B5 for <ppsp@ietf.org>; Tue, 8 May 2012 23:18:43 -0700 (PDT)
Received: from PEXHB012A.vu.local (130.37.236.66) by mailin.vu.nl (130.37.164.19) with Microsoft SMTP Server (TLS) id 14.2.283.3; Wed, 9 May 2012 08:18:41 +0200
Received: from [109.36.82.228] (130.37.238.20) by mails.vu.nl (130.37.236.66) with Microsoft SMTP Server (TLS) id 14.2.283.3; Wed, 9 May 2012 08:18:41 +0200
Message-ID: <4FAA0C76.9010306@cs.vu.nl>
Date: Wed, 09 May 2012 08:19:34 +0200
From: Arno Bakker <arno@cs.vu.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: zhangyunfei <zhangyunfei@chinamobile.com>
References: <OF97B14220.883D5968-ON482579DB.003454AD-482579DB.0035B23D@zte.com.cn> <2012041216393612240745@chinamobile.com>, <4F869775.6010007@cs.vu.nl> <2012041815001581776052@chinamobile.com>, <4F8E6DCE.90101@cs.vu.nl> <20120418183444961415101@chinamobile.com>
In-Reply-To: <20120418183444961415101@chinamobile.com>
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: 8bit
X-Originating-IP: [130.37.238.20]
Cc: ppsp <ppsp@ietf.org>
Subject: Re: [ppsp] [Spam] 回复: Re:回复: Re: Proposal to resolve Issue 10 + 13
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: arno@cs.vu.nl
List-Id: discussing to draw up peer to peer streaming protocol <ppsp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppsp>, <mailto:ppsp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ppsp>
List-Post: <mailto:ppsp@ietf.org>
List-Help: <mailto:ppsp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppsp>, <mailto:ppsp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2012 06:18:48 -0000

On 18/04/2012 12:34, zhangyunfei wrote:
> Hi Arno,
> Pls see inline.Thanks.

Hi all

this landed in my spam box, so sorry for the late reply. See inline.

> [Yunfei] This is what I worry about. We cannot assure that each time we 
> can request
> chunks in groups of powers of 2, as it's dependent on what the serving 
> peers have, which
> is hard to ensure that the number of available chunks being powers of 2. 

IMHO, chunks will be requested in powers of 2. First, one will likely
request more than 1 chunk at a time to be able to fill the pipeline from
sender to receiver (cf. delay-bandwidth product). Requesting 1K and then
waiting for it will not be efficient. Second, as we're computer
scientists we'll use base 2 (32K, 64K, etc) when using multiples ;o)


> In such cases, requsting
> a range of chunks needs no more bits than bin number. What's worse, if 
> the chunks peer A has is
> sparsely distributed, i.e., the chunkmap is likely to be 10001011110, 
> bin numbering needs more bits.

Bins are actually more efficient than (start,end) in this example. With
bin numbers, you'll in the worst case need an integer for every 1 in the
bitmap, so 6 in this case. In a better case we might be able to address
the 4 ones at the end as a single bin. However, if you use (start,end)
addressing, you'll actually need 2 integers per 1 bit, or 12 integers.

CU,
    Arno