All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: David Miller <davem@davemloft.net>,
	linux@horizon.com, Andrew Morton <akpm@linux-foundation.org>,
	netdev@vger.kernel.org
Subject: Re: [PATCH 0/4] Pull request for 'ipg-fixes' branch
Date: Sat, 12 Jan 2008 17:48:35 -0500	[thread overview]
Message-ID: <478943C3.2010805@garzik.org> (raw)
In-Reply-To: <20080110233508.GA13315@electric-eye.fr.zoreil.com>

Francois Romieu wrote:
> Please pull from branch 'ipg-fixes' in repository
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/romieu/netdev-2.6.git ipg-fixes
> 
> to get the changes below.
> 
> I have tested the driver with a PIV HT based motherboard. The network
> controller is connected to a fast ethernet switch (yeah, I'm cheap).
> A second host is performing two loop of scp in both direction for a
> 400Mb file. The files are sha1sumed after each scp. I have added a
> 'ping -q -f -l16' from the computer under test after some time.
> 
> After 35 copies from the computer under test and 28 copies to it
> (the ping eats a bit):
>              total       used       free     shared    buffers     cached
> Mem:       1019040    1003860      15180          0      20556     936792
> -/+ buffers/cache:      46512     972528
> Swap:      2031608          0    2031608
> 
> Before:
>              total       used       free     shared    buffers     cached
> Mem:       1019040     572036     447004          0      14988     525924
> -/+ buffers/cache:      31124     987916
> Swap:      2031608          0    2031608
> 
> /proc/slabinfo before and after the test are attached.
> 
> The driver is still a POMS but it seems better now.
> 
> I will not be available to work further on this issue before sunday.
> I'd appreciate being Cced though.
> 
> Distance from 'net-2.6/master' (27d1cba21fcc50c37eef5042c6be9fa7135e88fc)
> -------------------------------------------------------------------------
> 
> 286c83ce6e8263a5c4c55a57b4c1040800de0171
> d42f3afc953f9c99ffe84667a3ecf0d3b69f3d64
> 358bf4b8e8cbde5d6411b219e93a61728c892685
> a58cceed4464ba8ae94294184c15f43e92a5de89
> 
> Diffstat
> --------
> 
>  drivers/net/ipg.c |   36 ++++++++++++------------------------
>  1 files changed, 12 insertions(+), 24 deletions(-)

hrm... tried to pull this, but received non-ipg stuff too



  parent reply	other threads:[~2008-01-12 22:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-10 23:35 [PATCH 0/4] Pull request for 'ipg-fixes' branch Francois Romieu
2008-01-10 23:35 ` [PATCH 1/4] ipg: balance locking in irq handler Francois Romieu
2008-01-10 23:37 ` [PATCH 2/4] ipg: plug Tx completion leak Francois Romieu
2008-01-10 23:37 ` [PATCH 3/4] ipg: fix queue stop condition in the xmit handler Francois Romieu
2008-01-10 23:38 ` [PATCH 4/4] ipg: fix Tx completion irq request Francois Romieu
2008-01-11  1:58 ` [PATCH 0/4] Pull request for 'ipg-fixes' branch linux
2008-01-11 17:22   ` Francois Romieu
2008-01-12 22:48 ` Jeff Garzik [this message]
2008-01-13 15:50   ` Francois Romieu
2008-01-13 22:34     ` Francois Romieu

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=478943C3.2010805@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=linux@horizon.com \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.