Linux virtualization list
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, linux-kernel@vger.kernel.org
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	netdev@vger.kernel.org, Mikulas Patocka <mpatocka@redhat.com>,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] virtio_net: lower limit on buffer size
Date: Fri, 2 Jun 2017 12:34:57 +0300	[thread overview]
Message-ID: <3dd90d56-7110-bb9e-0b7f-4c8a8003a57f@cogentembedded.com> (raw)
In-Reply-To: <1496361148-4603-1-git-send-email-mst@redhat.com>

Hello!

On 6/2/2017 2:56 AM, Michael S. Tsirkin wrote:

> commit d85b758f72b0 "virtio_net: fix support for small rings"

    Commit d85b758f72b0 ("virtio_net: fix support for small rings")

> was supposed to increase the buffer size for small rings
> but had an unintentional side effect of decreasing
> it for large rings. This seems to break some setups -
> it's not yet clear why, but increasing buffer size
> back to what it was before helps.
>
> Fixes: d85b758f72b0 "virtio_net: fix support for small rings"

Fixes: d85b758f72b0 ("virtio_net: fix support for small rings")

> Reported-by: Mikulas Patocka <mpatocka@redhat.com>
> Reported-by: "J. Bruce Fields" <bfields@fieldses.org>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
[...]

MBR, Sergei

  parent reply	other threads:[~2017-06-02  9:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-01 23:56 [PATCH] virtio_net: lower limit on buffer size Michael S. Tsirkin
2017-06-02  1:57 ` J. Bruce Fields
2017-06-02  9:34 ` Sergei Shtylyov [this message]
2017-06-02 20:25   ` J. Bruce Fields
     [not found]   ` <20170602202536.GA24411@fieldses.org>
2017-06-03 20:17     ` Sergei Shtylyov
     [not found]     ` <aafb81af-54f2-06b0-3b5c-2713bc28184b@cogentembedded.com>
2017-06-05 19:36       ` J. Bruce Fields
2017-06-02 13:16 ` Mikulas Patocka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3dd90d56-7110-bb9e-0b7f-4c8a8003a57f@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox