From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johann Baudy Subject: Re: [PATCH] TX_RING and packet mmap Date: Tue, 21 Apr 2009 23:05:27 +0200 Message-ID: <7e0dd21a0904211405h488cbbc0j4e5c197789cc28ae@mail.gmail.com> References: <1238701718.5669.26.camel@bender> <7e0dd21a0904211313p73143cc8t51b5c537c5edfb05@mail.gmail.com> <7e0dd21a0904211346p523b1e1fo7f8ec7bd18ad87cf@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, Evgeniy Polyakov To: Christoph Lameter Return-path: Received: from mail-fx0-f158.google.com ([209.85.220.158]:63024 "EHLO mail-fx0-f158.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755878AbZDUVF3 (ORCPT ); Tue, 21 Apr 2009 17:05:29 -0400 Received: by fxm2 with SMTP id 2so2750764fxm.37 for ; Tue, 21 Apr 2009 14:05:27 -0700 (PDT) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: > Well yes. But I guess you know best what to call them. Just make them > more decriptive of their function. Yes, I understand, but I'm just afraid of backward compatibility with libraries that are currently using packet_mmap for RX ring. If I rename those TP_STATUS_KERNEL into TP_STATUS_AVAILABLE. I will break this compatibility. (for compilation).