All of lore.kernel.org
 help / color / mirror / Atom feed
From: Indrek Kruusa <indrek.kruusa@tuleriit.ee>
To: linux-kernel@vger.kernel.org
Subject: DSP like TCP/IP processing in linux kernel
Date: Wed, 12 Jan 2005 03:18:03 +0200	[thread overview]
Message-ID: <41E47ACB.4000905@tuleriit.ee> (raw)

Hi!

My goal is to:
- learn more about DSP like TCP/IP processing
- investigate network/transport layer implementation in Linux
- investigate the possibility to increase network performance by SIMD 
processing
- maybe compile some kind of document from my work
- ask lot of questions here :)


There are lot of quite basic questions to think about. The most basic is 
how to cope with SIMD at all.

Hardware
----------
CPU + ext. == DSP?
(+) SIMD (vertical/horisontal vectorized processing)
(-) (??) h/w MAC/shifter/flow control, separate x/y path

* ARM/MIPS/PowerPC/SPARC/x86 - they all have (or planned) somekind of 
SIMD extension but how much theory I can borrow from DSP world for SIMD 
CPUs? (quite a lot I think)
* network processors (Intel,Broadcom etc.) - can I borrow something from 
there? (only maybe how/why work is distributed between multiple cores)


Software (compiler)
--------------------
Is it possible at all to build a framework to cover those different 
ext.'s in common way?
* gcc builtins for particular arch (well, arm,x86,powerpc are there)
* intrinsics. only intel (?)
* somekind of layer above gcc builtins? (ehh...)

Tools
-------
How should I produce SIMD code?
* Which tools I have to work with SIMD ext.? (umm...vim)
* Which way I should choose: "look, feel and think" or pure math and 
modelling? (I don't like J.B.J. Fourier...)


Method
-------
How to start?
* tracing, profiling - squeeze out the performance hotspot and optimize 
it (is the underlying design suitable at all for this?)
* sketch down current implementation in linux and think again about 
whole thing (results after one year...for me :) )
* in networking context: start with the most common part: calculate 
checksums for IP and TCP (I like this idea)
* Forget about it: turn on -ftree-vectorize when gcc 4.x is here (no-no...)
* Forget about it: this kind of tweaking is not for Linux kernel (what 
about RAID-6 driver? :) )


Well, before I look into Documentation/, kernelnewbies.org, source etc. 
I'd like to ask: is it worth to go further? At least I hope so :)


thanks,
Indrek


                 reply	other threads:[~2005-01-12  1:18 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=41E47ACB.4000905@tuleriit.ee \
    --to=indrek.kruusa@tuleriit.ee \
    --cc=linux-kernel@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 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.