netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: Roy Sigurd Karlsbakk <roy@karlsbakk.net>,
	netdev@oss.sgi.com,
	Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND] tuning linux for high network performance?
Date: Thu, 24 Oct 2002 12:50:31 +0100	[thread overview]
Message-ID: <20021024125030.A7529@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200210241129.g9OBTpp09266@Port.imtp.ilyichevsk.odessa.ua>; from vda@port.imtp.ilyichevsk.odessa.ua on Thu, Oct 24, 2002 at 02:22:25PM -0200

On Thu, Oct 24, 2002 at 02:22:25PM -0200, Denis Vlasenko wrote:
> Please delete memory.o, rerun make bzImage, capture gcc
> command used for compiling memory.c, modify it:
> 
> gcc ... -o memory.o  ->  gcc ... -S -o memory.s ...

Have you tried make mm/memory.s ?

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html

  reply	other threads:[~2002-10-24 11:50 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-23 10:18 tuning linux for high network performance? Roy Sigurd Karlsbakk
2002-10-23 11:06 ` [RESEND] " Roy Sigurd Karlsbakk
2002-10-23 13:01   ` bert hubert
2002-10-23 13:21     ` David S. Miller
2002-10-23 13:42       ` Roy Sigurd Karlsbakk
2002-10-23 17:01         ` bert hubert
2002-10-23 17:10           ` Ben Greear
2002-10-23 17:11           ` Richard B. Johnson
2002-10-23 17:12           ` Nivedita Singhvi
2002-10-23 17:56             ` Richard B. Johnson
2002-10-23 18:07               ` Nivedita Singhvi
2002-10-23 18:30                 ` Richard B. Johnson
2002-10-24  4:11         ` David S. Miller
2002-10-24  9:37           ` Karen Shaeffer
2002-10-24 10:30           ` sendfile64() anyone? (was [RESEND] tuning linux for high network performance?) Roy Sigurd Karlsbakk
2002-10-24 10:47             ` David S. Miller
2002-10-24 11:07               ` Roy Sigurd Karlsbakk
2002-10-23 13:41     ` [RESEND] tuning linux for high network performance? Roy Sigurd Karlsbakk
2002-10-23 14:59     ` Nivedita Singhvi
2002-10-23 15:26       ` O_DIRECT sockets? (was [RESEND] tuning linux for high network performance?) Roy Sigurd Karlsbakk
2002-10-23 16:34         ` Nivedita Singhvi
2002-10-24 10:14           ` Roy Sigurd Karlsbakk
2002-10-24 10:46             ` David S. Miller
2002-10-23 18:01   ` [RESEND] tuning linux for high network performance? Denis Vlasenko
2002-10-23 13:36     ` Roy Sigurd Karlsbakk
2002-10-24 16:22       ` Denis Vlasenko
2002-10-24 11:50         ` Russell King [this message]
2002-10-24 12:42           ` bert hubert
2002-10-24 17:41           ` Denis Vlasenko
2002-10-25 11:36             ` Csum and csum copyroutines benchmark Denis Vlasenko
2002-10-25  7:48               ` Momchil Velikov
2002-10-25 13:59                 ` Denis Vlasenko
2002-10-25  9:47                   ` Momchil Velikov
2002-10-25 10:19                   ` Alan Cox
2002-10-25 16:00                     ` Denis Vlasenko
2002-10-23 14:52     ` [RESEND] tuning linux for high network performance? Nivedita Singhvi

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=20021024125030.A7529@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=roy@karlsbakk.net \
    --cc=vda@port.imtp.ilyichevsk.odessa.ua \
    /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).