Hi Peter, > >> > 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. that would work as well. We will see what works out best by giving application the least amount of hassle :) Regards Marcel -- 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
