linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: kys@microsoft.com
Cc: David.Laight@ACULAB.COM, alexander.duyck@gmail.com,
	haiyangz@microsoft.com, vkuznets@redhat.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	jasowang@redhat.com
Subject: Re: [PATCH net-next RFC] net: increase LL_MAX_HEADER for Hyper-V
Date: Thu, 17 Sep 2015 11:52:18 -0700 (PDT)	[thread overview]
Message-ID: <20150917.115218.655587837796826886.davem@davemloft.net> (raw)
In-Reply-To: <BY2PR0301MB16547020327B59C72692E730A05A0@BY2PR0301MB1654.namprd03.prod.outlook.com>

From: KY Srinivasan <kys@microsoft.com>
Date: Thu, 17 Sep 2015 15:14:05 +0000

> I think I can achieve my original goal of not having any allocation
> in the send path by carefully using the memory available in the skb:

Please stop flat-out ignoring David L.'s suggestion.

Have a pre-cooked ring of buffers for these descriptors that you can
point the chip at.  No per-packet allocation is necessary at all.

If you play games with SKBs you will get burned.

  reply	other threads:[~2015-09-17 18:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16 15:50 [PATCH net-next RFC] net: increase LL_MAX_HEADER for Hyper-V Vitaly Kuznetsov
2015-09-16 16:08 ` Haiyang Zhang
2015-09-16 16:25   ` David Laight
2015-09-16 17:26     ` Alexander Duyck
2015-09-16 17:55     ` KY Srinivasan
2015-09-16 21:38       ` Alexander Duyck
2015-09-16 22:57         ` KY Srinivasan
2015-09-16 23:48           ` Alexander Duyck
2015-09-16 23:58             ` KY Srinivasan
2015-09-17  8:38           ` David Laight
2015-09-17 15:14             ` KY Srinivasan
2015-09-17 18:52               ` David Miller [this message]
2015-09-17 19:52                 ` KY Srinivasan
2015-09-17 20:10                   ` David Miller
2015-09-17 21:16                     ` KY Srinivasan
2015-09-16 17:59     ` David Miller
2015-09-17  9:03       ` Vitaly Kuznetsov

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=20150917.115218.655587837796826886.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=David.Laight@ACULAB.COM \
    --cc=alexander.duyck@gmail.com \
    --cc=haiyangz@microsoft.com \
    --cc=jasowang@redhat.com \
    --cc=kys@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=vkuznets@redhat.com \
    /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).