netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: <akiyano@amazon.com>
Cc: brouer@redhat.com, davem@davemloft.net, netdev@vger.kernel.org,
	"David Woodhouse" <dwmw@amazon.com>,
	zorik@amazon.com, matua@amazon.com, saeedb@amazon.com,
	msw@amazon.com, aliguori@amazon.com, nafea@amazon.com,
	gtzalik@amazon.com, netanel@amazon.com, alisaidi@amazon.com,
	"Björn Töpel" <bjorn.topel@intel.com>
Subject: Re: [PATCH V1 net-next 00/12] Improving performance and reducing latencies, by using latest capabilities exposed in ENA device
Date: Tue, 9 Oct 2018 21:30:17 +0200	[thread overview]
Message-ID: <20181009213017.653ed630@redhat.com> (raw)
In-Reply-To: <1539110709-31954-1-git-send-email-akiyano@amazon.com>


On Tue, 9 Oct 2018 21:44:57 +0300 <akiyano@amazon.com> wrote:

> From: Arthur Kiyanovski <akiyano@amazon.com>
> 
> This patchset introduces the following:
> 1. A new placement policy of Tx headers and descriptors, which takes
> advantage of an option to place headers + descriptors in device memory
> space. This is sometimes referred to as LLQ - low latency queue.
> The patch set defines the admin capability, maps the device memory as
> write-combined, and adds a mode in transmit datapath to do header +
> descriptor placement on the device.
> 2. Support for RX checksum offloading
> 3. Miscelaneous small improvements and code cleanups

What are your plans for XDP?

You are unsure ask your-colleague David Woodhouse, who I've discussed
this with when he attended my talk at Kernel-Recipes[1], slide[2].

[1] https://kernel-recipes.org/en/2018/talks/xdp-a-new-programmable-network-layer/
[2] http://people.netfilter.org/hawk/presentations/KernelRecipes2018/XDP_Kernel_Recipes_2018.pdf
-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  LinkedIn: http://www.linkedin.com/in/brouer

  parent reply	other threads:[~2018-10-10  2:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-09 18:44 [PATCH V1 net-next 00/12] Improving performance and reducing latencies, by using latest capabilities exposed in ENA device akiyano
2018-10-09 18:44 ` [PATCH V1 net-next 01/12] net: ena: minor performance improvement akiyano
2018-10-09 18:44 ` [PATCH V1 net-next 02/12] net: ena: complete host info to match latest ENA spec akiyano
2018-10-09 18:45 ` [PATCH V1 net-next 03/12] net: ena: introduce Low Latency Queues data structures according to " akiyano
2018-10-09 18:45 ` [PATCH V1 net-next 04/12] net: ena: add functions for handling Low Latency Queues in ena_com akiyano
2018-10-09 18:45 ` [PATCH V1 net-next 05/12] net: ena: add functions for handling Low Latency Queues in ena_netdev akiyano
2018-10-09 18:45 ` [PATCH V1 net-next 06/12] net: ena: use CSUM_CHECKED device indication to report skb's checksum status akiyano
2018-10-09 18:45 ` [PATCH V1 net-next 07/12] net: ena: explicit casting and initialization, and clearer error handling akiyano
2018-10-09 18:45 ` [PATCH V1 net-next 08/12] net: ena: limit refill Rx threshold to 256 to avoid latency issues akiyano
2018-10-09 18:45 ` [PATCH V1 net-next 09/12] net: ena: change rx copybreak default to reduce kernel memory pressure akiyano
2018-10-09 18:45 ` [PATCH V1 net-next 10/12] net: ena: remove redundant parameter in ena_com_admin_init() akiyano
2018-10-09 18:45 ` [PATCH V1 net-next 11/12] net: ena: update driver version to 2.0.1 akiyano
2018-10-09 18:45 ` [PATCH V1 net-next 12/12] net: ena: fix indentations in ena_defs for better readability akiyano
2018-10-09 19:30 ` Jesper Dangaard Brouer [this message]
2018-10-09 19:33   ` [PATCH V1 net-next 00/12] Improving performance and reducing latencies, by using latest capabilities exposed in ENA device Bshara, Nafea
2018-10-09 21:18     ` Bshara, Saeed
2018-10-10 10:15       ` Jesper Dangaard Brouer
2018-10-09 20:54 ` Machulsky, Zorik
2018-10-11  5:41 ` David Miller
2018-10-11  7:53   ` Kiyanovski, Arthur

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=20181009213017.653ed630@redhat.com \
    --to=brouer@redhat.com \
    --cc=akiyano@amazon.com \
    --cc=aliguori@amazon.com \
    --cc=alisaidi@amazon.com \
    --cc=bjorn.topel@intel.com \
    --cc=davem@davemloft.net \
    --cc=dwmw@amazon.com \
    --cc=gtzalik@amazon.com \
    --cc=matua@amazon.com \
    --cc=msw@amazon.com \
    --cc=nafea@amazon.com \
    --cc=netanel@amazon.com \
    --cc=netdev@vger.kernel.org \
    --cc=saeedb@amazon.com \
    --cc=zorik@amazon.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).