[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20140116.173737.429918297549548812.davem@davemloft.net>
Date: Thu, 16 Jan 2014 17:37:37 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: jasowang@...hat.com
Cc: virtualization@...ts.linux-foundation.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, rusty@...tcorp.com.au, mst@...hat.com
Subject: Re: [PATCH net-next] virtio-net: drop rq->max and rq->num
From: Jason Wang <jasowang@...hat.com>
Date: Thu, 16 Jan 2014 14:45:24 +0800
> It looks like there's no need for those two fields:
>
> - Unless there's a failure for the first refill try, rq->max should be always
> equal to the vring size.
> - rq->num is only used to determine the condition that we need to do the refill,
> we could check vq->num_free instead.
> - rq->num was required to be increased or decreased explicitly after each
> get/put which results a bad API.
>
> So this patch removes them both to make the code simpler.
>
> Cc: Rusty Russell <rusty@...tcorp.com.au>
> Cc: Michael S. Tsirkin <mst@...hat.com>
> Signed-off-by: Jason Wang <jasowang@...hat.com>
> Acked-by: Rusty Russell <rusty@...tcorp.com.au>
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists