On Thu, Nov 2, 2017 at 12:51 PM, Jason Wang wrote:
>
>
> On 2017年11月02日 11:45, Michael S. Tsirkin wrote:
>>
>> On Thu, Nov 02, 2017 at 11:43:48AM +0800, Jason Wang wrote:
>>>
>>>
>>> On 2017年11月02日 09:11, Willem de Bruijn wrote:
On Tue, Oct 31, 2017 at 7:32 PM, Jason Wang wrote:
>
>
On 2017年11月02日 11:45, Michael S. Tsirkin wrote:
On Thu, Nov 02, 2017 at 11:43:48AM +0800, Jason Wang wrote:
On 2017年11月02日 09:11, Willem de Bruijn wrote:
On Tue, Oct 31, 2017 at 7:32 PM, Jason Wang wrote:
tun now use flow caches based automatic queue steering method. This
may not suffice a
On Thu, Nov 02, 2017 at 11:43:48AM +0800, Jason Wang wrote:
>
>
> On 2017年11月02日 09:11, Willem de Bruijn wrote:
> > On Tue, Oct 31, 2017 at 7:32 PM, Jason Wang wrote:
> > > tun now use flow caches based automatic queue steering method. This
> > > may not suffice all user cases. To extend it to b
On 2017年11月02日 09:11, Willem de Bruijn wrote:
On Tue, Oct 31, 2017 at 7:32 PM, Jason Wang wrote:
tun now use flow caches based automatic queue steering method. This
may not suffice all user cases. To extend it to be able to use more
flow steering policy, this patch abstracts flow steering log
On Tue, Oct 31, 2017 at 7:32 PM, Jason Wang wrote:
> tun now use flow caches based automatic queue steering method. This
> may not suffice all user cases. To extend it to be able to use more
> flow steering policy, this patch abstracts flow steering logic into
> tun_steering_ops, then we can decla
tun now use flow caches based automatic queue steering method. This
may not suffice all user cases. To extend it to be able to use more
flow steering policy, this patch abstracts flow steering logic into
tun_steering_ops, then we can declare and use different methods in
the future.
Signed-off-by: