From: Chris Snook <csnook@redhat.com>
To: Jay Cliburn <jacliburn@bellsouth.net>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-kernel@vger.kernel.org, atl1-devel@lists.sourceforge.net,
netdev@vger.kernel.org
Subject: Re: [PATCH 09/26] atl1: refactor tx processing
Date: Thu, 24 Jan 2008 20:08:03 -0500 [thread overview]
Message-ID: <47993673.7040408@redhat.com> (raw)
In-Reply-To: <20080124190024.1b81238e@osprey.hogchain.net>
Jay Cliburn wrote:
> On Tue, 22 Jan 2008 18:31:09 -0600
> Jay Cliburn <jacliburn@bellsouth.net> wrote:
>
>> On Tue, 22 Jan 2008 04:58:17 -0500
>> Jeff Garzik <jeff@garzik.org> wrote:
>>
> [...]
>>> for such a huge patch, this description is very tiny. [describe]
>>> what is refactored, and why.
>
> Is this one any better?
This satisfies me.
Acked-by: Chris Snook <csnook@redhat.com>
> From df475e2eea401f9dc18ca23dab538b99fb9e710c Mon Sep 17 00:00:00 2001
> From: Jay Cliburn <jacliburn@bellsouth.net>
> Date: Wed, 23 Jan 2008 21:36:36 -0600
> Subject: [PATCH] atl1: simplify tx packet descriptor
>
> The transmit packet descriptor consists of four 32-bit words, with word 3
> upper bits overloaded depending upon the condition of its bits 3 and 4.
> The driver currently duplicates all word 2 and some word 3 register bit
> definitions unnecessarily and also uses a set of nested structures in its
> definition of the TPD without good cause. This patch adds a lengthy
> comment describing the TPD, eliminates duplicate TPD bit definitions,
> and simplifies the TPD structure itself. It also expands the TSO check
> to correctly handle custom checksum versus TSO processing using the revised
> TPD definitions. Finally, shorten some variable names in the transmit
> processing path to reduce line lengths, rename some variables to better
> describe their purpose (e.g., nseg versus m), and add a comment or two
> to better describe what the code is doing.
>
> Signed-off-by: Jay Cliburn <jacliburn@bellsouth.net>
next prev parent reply other threads:[~2008-01-25 1:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1199152804-3889-1-git-send-email-jacliburn@bellsouth.net>
[not found] ` <1199152804-3889-26-git-send-email-jacliburn@bellsouth.net>
2008-01-01 18:15 ` [PATCH 25/26] [REVISED] atl1: add NAPI support Jay Cliburn
2008-01-02 2:56 ` Joonwoo Park
2008-01-02 3:07 ` David Miller
[not found] ` <1199152804-3889-10-git-send-email-jacliburn@bellsouth.net>
[not found] ` <4795BE39.6000505@garzik.org>
2008-01-23 0:31 ` [PATCH 09/26] atl1: refactor tx processing Jay Cliburn
2008-01-25 1:00 ` Jay Cliburn
2008-01-25 1:08 ` Chris Snook [this message]
2008-01-25 3:01 ` Jeff Garzik
[not found] ` <1199152804-3889-7-git-send-email-jacliburn@bellsouth.net>
[not found] ` <4795BDBB.10904@garzik.org>
2008-01-23 2:13 ` [PATCH 06/26] atl1: update initialization parameters Jay Cliburn
2008-01-23 2:19 ` Jeff Garzik
2008-01-23 2:30 ` Chris Snook
2008-01-01 2:22 [PATCH 00/26] atl1: divide and modernize Jay Cliburn
2008-01-01 2:22 ` [PATCH 09/26] atl1: refactor tx processing Jay Cliburn
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=47993673.7040408@redhat.com \
--to=csnook@redhat.com \
--cc=atl1-devel@lists.sourceforge.net \
--cc=jacliburn@bellsouth.net \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).