public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Carcellelist <carcellelist@free.fr>
To: b.a.t.m.a.n@open-mesh.net
Subject: Re: [B.A.T.M.A.N.] batman-adv use in Manchester NH
Date: Tue, 5 May 2009 19:34:35 +0200	[thread overview]
Message-ID: <200905051935.03639.carcellelist@free.fr> (raw)
In-Reply-To: <bad82a80905050708x1f0a75f0j27e78d72c81201bc@mail.gmail.com>

Hi Arc,

> What kind of traffic throughput is the kernel module capable of?  Does the
> module multithread properly for multicore utilization?  Would a FPGA
> variant be needed to have a "mesh switch" or would a high-end multicore ARM
> be reasonably able to handle say an 8-port gigabit mesh switch?

Concerning the multithreading of the batman daemon, if batman supports multi-
threads, you can distribute this on different cores definitely:

Concerning FPGA and the batman daemon (both userspace and kernelspace), it 
will depend on the FPGA you want to use (FPGAs from the two major vendors, 
Xilinx and Altera, are divided into two families based on the number of 
logical gates they have - huge Xilinx VIRTEX5 and coming 6 are even embarking 
one or event 2 PowerPCs next to the FPGA gates). Large FPGAs could embark part 
of the daemon in the CPU hardwired in the chip and the rest (for instance 
intensive functions like packet routing and filtering). Small FPGAs would run 
the daemon in the softcore (OpenRISC, Microblaze, aEMB) either "userspace" or 
"kernelspace" in the softcore or directly with the daemon in low level langage 
(VHDL or VERILOG) after porting the C code into this HDL langages. Core-
networking routers from CISCO, JUNIPER are loaded with FPGAs to process the 
packet filtering and routing the closest from the physical layer.

Concerning ARM and 8-port gigabit mesh switch, the power of even a coming 
multicore ARM13 would not be sufficient to run the packet routing and 
filtering for the 8xGigabits ports. ARM had been primarly developed for 
embedded devices and not for powerful applications such as switching and 
routing.

Xavier.

  parent reply	other threads:[~2009-05-05 17:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-05 14:08 [B.A.T.M.A.N.] batman-adv use in Manchester NH Arc Riley
2009-05-05 16:05 ` Marek Lindner
2009-05-05 18:11   ` Arc Riley
2009-05-06  5:15     ` Marek Lindner
2009-05-06  5:48       ` Antoine van Gelder
2009-05-06  7:18         ` Marek Lindner
2009-05-06  9:49           ` [B.A.T.M.A.N.] [PATCH] Add switch for vis daemon to serve mesh topology in JSON format Antoine van Gelder
2009-05-06  9:51           ` [B.A.T.M.A.N.] batman-adv use in Manchester NH Antoine van Gelder
2009-05-06  9:58           ` [B.A.T.M.A.N.] [PATCH] Add switch for vis daemon to serve mesh topology in JSON format - TAKE 2 Antoine van Gelder
2009-05-05 17:26 ` [B.A.T.M.A.N.] batman-adv use in Manchester NH Dennis Bartsch
2009-05-05 17:34   ` Charles Wyble
2009-05-05 17:34 ` Carcellelist [this message]
2009-05-05 18:29 ` Charles Wyble
2009-05-05 18:53   ` Arc Riley
2009-05-07 10:08     ` Simon Wunderlich
2009-05-06  5:18   ` Marek Lindner

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=200905051935.03639.carcellelist@free.fr \
    --to=carcellelist@free.fr \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /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