From: Arnd Bergmann <arnd@arndb.de>
To: Yoshinori Sato <ysato@users.sourceforge.jp>
Cc: Guenter Roeck <linux@roeck-us.net>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH v12 00/21] Re-introduce h8300 architecture
Date: Tue, 12 May 2015 09:29:54 +0200 [thread overview]
Message-ID: <9302360.f2Sv7QXQxG@wuerfel> (raw)
In-Reply-To: <87sib2pbsu.wl-ysato@users.sourceforge.jp>
On Tuesday 12 May 2015 15:09:05 Yoshinori Sato wrote:
> > It would be better to do one of two things:
> >
> > a) use the code from lib/checksum.c that is known to work well, and that
> > contains all the necessary exports. It seems that the h8300 is
> > almost an except copy of the generic code, it just misses a few
> > improvements that were done already in the kernel.
> >
> > b) provide an optimized implementation written in assembly where necessary.
> > This can provide a significant performance improvement for TCP/IP
> > networking.
>
> I think option a.
> It was being written by an assembler before, so that was just left.
Ok, sounds good. You can always change this to b) later if you run into
networking performance bottlenecks in the kernel.
Arnd
next prev parent reply other threads:[~2015-05-12 7:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 6:26 Yoshinori Sato
2015-05-11 6:26 ` [PATCH v12 01/21] MAINTAINERS: Add H8/300 entry Yoshinori Sato
2015-05-11 6:26 ` [PATCH v12 02/21] mksysmap: Add h8300 local symbol pattern Yoshinori Sato
2015-05-11 6:26 ` [PATCH v12 03/21] Add ELF machine Yoshinori Sato
2015-05-11 6:26 ` [PATCH v12 04/21] sh-sci: Add h8300 SCI Yoshinori Sato
2015-05-11 6:26 ` [PATCH v12 05/21] asm-generic: Add common asm-offsets.h Yoshinori Sato
2015-05-11 6:26 ` [PATCH v12 06/21] h8300: Assembly headers Yoshinori Sato
2015-05-11 6:26 ` [PATCH v12 07/21] h8300: UAPI headers Yoshinori Sato
2015-05-11 6:26 ` [PATCH v12 08/21] h8300: Interrupt and exceptions Yoshinori Sato
2015-05-11 6:26 ` [PATCH v12 09/21] h8300: kernel startup Yoshinori Sato
2015-05-11 6:26 ` [PATCH v12 10/21] h8300: Low level entry Yoshinori Sato
2015-05-11 6:26 ` [PATCH v12 11/21] h8300: compressed image support Yoshinori Sato
2015-05-11 6:26 ` [PATCH v12 12/21] h8300: process helpers Yoshinori Sato
2015-05-11 6:26 ` [PATCH v12 13/21] h8300: miscellaneous functions Yoshinori Sato
2015-05-11 6:26 ` [PATCH v12 14/21] h8300: Memory management Yoshinori Sato
2015-05-11 6:26 ` [PATCH v12 15/21] h8300: library functions Yoshinori Sato
2015-05-11 6:26 ` [PATCH v12 16/21] h8300: Build scripts Yoshinori Sato
2015-05-11 6:26 ` [PATCH v12 17/21] h8300: clock driver Yoshinori Sato
2015-08-08 0:43 ` Michael Turquette
2015-05-11 6:26 ` [PATCH v12 18/21] h8300: clocksource Yoshinori Sato
2015-05-11 6:26 ` [PATCH v12 19/21] h8300: IRQ chip driver Yoshinori Sato
2015-05-11 6:26 ` [PATCH v12 20/21] h8300: configs Yoshinori Sato
2015-05-11 6:26 ` [PATCH v12 21/21] h8300: devicetree source Yoshinori Sato
2015-05-11 17:50 ` [PATCH v12 00/21] Re-introduce h8300 architecture Guenter Roeck
2015-05-11 19:04 ` Arnd Bergmann
2015-05-12 6:09 ` Yoshinori Sato
2015-05-12 7:29 ` Arnd Bergmann [this message]
2015-05-12 4:53 ` Yoshinori Sato
2015-05-12 13:07 ` Guenter Roeck
2015-05-12 15:46 ` Yoshinori Sato
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=9302360.f2Sv7QXQxG@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=ysato@users.sourceforge.jp \
/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
all inboxes | Powered by JetHome®