From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v1] net/tap: return empty port offload capabilities Date: Wed, 25 Apr 2018 18:47:51 +0200 Message-ID: <1822119.1fBLbGrzlv@xps> References: <1524672957-4018-1-git-send-email-ophirmu@mellanox.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Pascal Mazon , Olga Shern , stable@dpdk.org To: Ophir Munk , Ferruh Yigit Return-path: In-Reply-To: <1524672957-4018-1-git-send-email-ophirmu@mellanox.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 25/04/2018 18:15, Ophir Munk: > Fix report on port offload capabilities to be 0 (no capabilities). > Before this commit port capabilities were a clone of queue > capabilities, however the current TAP offload capabilities (e.g. > checksum calculation) are per queue and are not specific per port. I did not follow what is the problem exactly. But this change looks wrong to me. Please look at the thread "Survey for final decision about per-port offload API" http://dpdk.org/ml/archives/dev/2018-March/094459.html It says: "every queue capabilities must be reported as port capabilities"