Thread (21 messages) flat view 21 messages, 4 authors, 2012-09-10

Re: [PATCH v2 2/2] virtio-ring: Allocate indirect buffers from cache when possible

From: "Michael S. Tsirkin" <mst@redhat.com>
Date: 2012-08-29 22:51:37
Also in: kvm, lkml

On Wed, Aug 29, 2012 at 10:46:19PM +0200, Sasha Levin wrote:
On 08/29/2012 08:12 PM, Michael S. Tsirkin wrote:
quoted
quoted
quoted
quoted
quoted
What is a good default for net? I guess max sg?
I think that it depends on the workload. I'd say we should keep the default to 0
(disabled) unless we can have a good way to adjust it to the load.
For *all* drivers?

Then it is mostly useless. No one has the time to tweak module
parameters in real life.

For virtio-net, 16+1 is not too much and ensures we always
use the cache.

If that works better than 0 I would say run with 17.
I was being extra-cautious with leaving it disabled until specifically enabled
because I assumed that this would be one of the first comments I'll get if it
was enabled by default :)

If you're comfortable with setting it to a sane default like 17, I'm perfectly
fine with that as well.


Thanks,
Sasha
If our testing shows it helps and does not trigger regressions, then
why not? module params are mostly there for developers.
They are not all that helpful to users.
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help