netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: netdev@vger.kernel.org
Subject: Re: tun mq failure
Date: Wed, 23 Jan 2013 15:18:45 +0200	[thread overview]
Message-ID: <20130123131845.GB18276@redhat.com> (raw)
In-Reply-To: <50FFD2A7.6010402@redhat.com>

On Wed, Jan 23, 2013 at 08:08:07PM +0800, Jason Wang wrote:
> On 01/23/2013 07:06 PM, Hannes Frederic Sowa wrote:
> > On Wed, Jan 23, 2013 at 12:05:16PM +0200, Michael S. Tsirkin wrote:
> >> This is when trying to start a VPN using some old openvpn binary so MQ
> >> is not set.
> >>
> >> So
> >> 1. I think we should limit allocation of MQ to when MQ flag is set in SETIFF.
> >> 2. order 7 allocation is 2^^7 pages - about half a megabyte of contigious
> >>    memory. This is quite likely to fail.
> >>    Let's start with a small limit on number of queues, like 8?
> >>    Then we know it will succeed.
> >>    Longer term we might want to solve it differently.
> > This has been come up before:
> > http://thread.gmane.org/gmane.linux.network/255647/focus=255902
> >
> > I think a solution to this problem is still outstanding.
> >
> I draft a patch in the reply of in that thread, but didn't get feedback
> from reporter.

Yes it's essentialy same.
So can you please submit an official patch with proper
subject commit log and signature?

  reply	other threads:[~2013-01-23 13:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 10:05 tun mq failure Michael S. Tsirkin
2013-01-23 11:06 ` Hannes Frederic Sowa
2013-01-23 11:41   ` Michael S. Tsirkin
2013-01-23 12:10     ` Jason Wang
2013-01-23 13:18       ` Michael S. Tsirkin
2013-01-23 12:08   ` Jason Wang
2013-01-23 13:18     ` Michael S. Tsirkin [this message]
2013-01-23 13:20       ` Jason Wang

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=20130123131845.GB18276@redhat.com \
    --to=mst@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).