From: Ian Campbell <ian.campbell@citrix•com>
To: George Dunlap <George.Dunlap@eu•citrix.com>
Cc: Malcolm Crossley <malcolm.crossley@citrix•com>,
Jonathan Davies <jonathan.davies@citrix•com>,
Wei Liu <Wei.Liu2@citrix•com>,
Eric Dumazet <eric.dumazet@gmail•com>,
Hideaki YOSHIFUJI <yoshfuji@linux-ipv6•org>,
netdev <netdev@vger•kernel.org>, James Morris <jmorris@namei•org>,
Patrick McHardy <kaber@trash•net>,
David Vrabel <david.vrabel@citrix•com>,
Alexey Kuznetsov <kuznet@ms2•inr.ac.ru>,
xen-devel <xen-devel@lists•xenproject.org>,
"Boris Ostrovsky" <boris.ostrovsky@oracle•com>,
"David S. Miller" <davem@davemloft•net>
Subject: Re: [Xen-devel] [PATCH RFC] tcp: Allow sk_wmem_alloc to exceed sysctl_tcp_limit_output_bytes
Date: Wed, 15 Apr 2015 15:36:23 +0100 [thread overview]
Message-ID: <1429108583.15516.304.camel@citrix.com> (raw)
In-Reply-To: <CAFLBxZaDPa0Em6z-bwg1HoLqCU9R_rWD8ri+0sNVgX-Httj_1A@mail.gmail.com>
On Wed, 2015-04-15 at 15:19 +0100, George Dunlap wrote:
> On Mon, Apr 13, 2015 at 4:03 PM, Malcolm Crossley
[...]
> > From a networking point of view, the backend is a switch. Is it OK to
> > consider the packet to have been transmitted from the guest point of
> > view once the backend is aware of the packet?
> >
> > This would help justify the skb_orphan() in the frontend.
>
> This sounds sensible to me, particularly if virtio_net is already doing it.
I also find Malcolm's argument above pretty compelling.
Ian.
next prev parent reply other threads:[~2015-04-15 14:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 16:46 [PATCH RFC] tcp: Allow sk_wmem_alloc to exceed sysctl_tcp_limit_output_bytes Jonathan Davies
2015-03-26 17:14 ` Eric Dumazet
2015-03-27 13:06 ` Jonathan Davies
2015-04-13 13:46 ` [Xen-devel] " David Vrabel
2015-04-13 14:05 ` Eric Dumazet
2015-04-13 15:03 ` Malcolm Crossley
2015-04-15 14:19 ` George Dunlap
2015-04-15 14:36 ` Ian Campbell [this message]
2015-04-15 16:42 ` Eric Dumazet
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=1429108583.15516.304.camel@citrix.com \
--to=ian.campbell@citrix$(echo .)com \
--cc=George.Dunlap@eu$(echo .)citrix.com \
--cc=Wei.Liu2@citrix$(echo .)com \
--cc=boris.ostrovsky@oracle$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=david.vrabel@citrix$(echo .)com \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=jmorris@namei$(echo .)org \
--cc=jonathan.davies@citrix$(echo .)com \
--cc=kaber@trash$(echo .)net \
--cc=kuznet@ms2$(echo .)inr.ac.ru \
--cc=malcolm.crossley@citrix$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=xen-devel@lists$(echo .)xenproject.org \
--cc=yoshfuji@linux-ipv6$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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