All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: Koichiro Den <den@klaipeden.com>, mst@redhat.com
Cc: netdev@vger.kernel.org, kvm@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 2/2] vhost-net: revert vhost_exceeds_maxpend logic to its original
Date: Mon, 21 Aug 2017 20:40:39 +0800	[thread overview]
Message-ID: <047bb207-cec6-ece5-470f-340d7c5ee7b7@redhat.com> (raw)
In-Reply-To: <0cbc33d6-eb1e-cea4-4cdf-a8a88932da62@redhat.com>



On 2017年08月21日 11:06, Jason Wang wrote:
>
>
> On 2017年08月19日 14:41, Koichiro Den wrote:
>> To depend on vq.num and the usage of VHOST_MAX_PEND is not succinct
>> and in some case unexpected, so revert its logic part only.
>
> Hi:
>
> Could you explain a little bit more on the case that is was not 
> sufficent?
>
> Thanks

Just have another thought.

I wonder whether or not just use ulimit(memlock) is better here. It 
looks more flexible.

Thanks
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  reply	other threads:[~2017-08-21 12:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-19  6:41 [PATCH 2/2] vhost-net: revert vhost_exceeds_maxpend logic to its original Koichiro Den
2017-08-21  3:06 ` Jason Wang
2017-08-21 12:40   ` Jason Wang [this message]
2017-08-21 13:32     ` Koichiro Den
2017-08-21 13:30   ` Koichiro Den
  -- strict thread matches above, loose matches on Subject: below --
2017-08-19  6:41 Koichiro Den

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=047bb207-cec6-ece5-470f-340d7c5ee7b7@redhat.com \
    --to=jasowang@redhat.com \
    --cc=den@klaipeden.com \
    --cc=kvm@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.