netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Daniel Borkmann <danborkmann@googlemail.com>
Cc: Matt Mackall <mpm@selenic.com>,
	David Miller <davem@davemloft.net>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	netdev@oss.sgi.com
Subject: Re: [PATCH] netpoll: allow execution of multiple rx_hooks per interface
Date: Wed, 13 Jan 2010 08:57:07 -0500	[thread overview]
Message-ID: <x49ljg25cr0.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <4B4D1372.9060702@gmail.com> (Daniel Borkmann's message of "Wed, 13 Jan 2010 01:27:30 +0100")

Daniel Borkmann <danborkmann@googlemail.com> writes:

> Daniel Borkmann wrote:
>> Matt Mackall wrote:
>>> On Mon, 2010-01-11 at 15:59 -0800, David Miller wrote:
>>>> From: Matt Mackall <mpm@selenic.com>
>>>> Date: Mon, 11 Jan 2010 17:21:48 -0600
>>>>
>>>>> Looks pretty good. Dave?
>>>>>
>>>>> Acked-by: Matt Mackall <mpm@selenic.com>
>>>> I don't like the loop for RX ARP processing.
>>>>
>>>> The packet contents aren't going to change, so doing basic
>>>> packet validation inside of the "for each RX client" loop
>>>> of arp_reply() doesn't make any sense.
>>> True. Dan, please help our poor compilers with some manual loop
>>> invariant motion.
>> 
>> Okay, true. I'll fix this by tomorrow and resend the patch.
>
> Here the fix of the RX ARP processing routine. Content that isn't
> going to change is out-of-loop.
> Successfully tested on my machines.

Against what tree does this patch apply?  It doesn't apply to Linus's
git tree.  Also, in the future, could you use the -p option to diff so
we can see what function or data structure is being modified?  It really
helps in reviewing.

Thanks!
Jeff

  reply	other threads:[~2010-01-13 13:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-06 20:54 [PATCH] netpoll: allow execution of multiple rx_hooks per interface Daniel Borkmann
2010-01-07  3:54 ` Matt Mackall
2010-01-07  9:02   ` David Miller
2010-01-07 19:06     ` Daniel Borkmann
2010-01-08  0:20       ` Daniel Borkmann
2010-01-11 23:21         ` Matt Mackall
2010-01-11 23:59           ` David Miller
2010-01-12  0:03             ` Matt Mackall
2010-01-12  0:09               ` Daniel Borkmann
2010-01-13  0:27                 ` Daniel Borkmann
2010-01-13 13:57                   ` Jeff Moyer [this message]
2010-01-13 16:53                     ` Daniel Borkmann
2010-01-14  4:41                   ` David Miller

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=x49ljg25cr0.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=danborkmann@googlemail.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=netdev@oss.sgi.com \
    --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).