Hi, Gustavo and Marcel, > Hi Peter, > > * Peter Krystad <pkrystad@xxxxxxxxxxxxxx> [2010-08-02 18:30:34 -0700]: > >> >> Hi Marcel and Kevin, >> >> >> > >> >> > Agree that it should be done "in background" and that a size >> >> threshold would be useful. But who evaluates that threshold? The >> >> bluez kernel components, which essentially implement a transport >> >> driver, should not be examining objects (files, phonebooks, etc) size >> >> to see if this threshold is met. Therefore, it would seem Tim's >> >> suggestion of having the profile send a 'prefer_amp' bit would be >> >> useful, right? >> >> >> >> I would do something like "prefer_amp when over 100kb" or something. >> >> And >> >> then the kernel needs to count. Meaning the L2CAP layer could easily >> >> count this by itself. >> > >> > What? Let's say the effect we want is that if the object is greater >> > than, say, 10 megabytes, then we want to use AMP for the transfer. >> > With your scheme, you want the kernel to count up to 10 megabytes, >> > THEN switch over to AMP? >> > No, you don't, he says rhetorically. :) >> >> If the policy was defined as "prefer_amp after n seconds" we would get >> the desired effect without having to do any counting in the kernel. > > In both cases we have to take in account the total size of the file, or > the estimated time of transfer, so we can avoid to move to AMP when the > transfer is about to end. Right! Don't want to switch to AMP just to push those last 100 bytes :) Since the kernel does not know the total object size to be transferred, (right?), I've yet to come up with any 'threshold' ideas the kernel can make. Note that the transfer could be one huge file or many small ones. -- Tim Monahan-Mitchell Employee of Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
