From: rixed@happyleptic.org
To: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] IPv6 packet parsing
Date: Fri, 18 Oct 2013 14:16:12 +0200 [thread overview]
Message-ID: <20131018121612.GB28679@ombreroze.happyleptic.org> (raw)
In-Reply-To: <20131018115955.GG25839@dark.recoil.org>
-[ Fri, Oct 18, 2013 at 12:59:55PM +0100, Anil Madhavapeddy ]----
> One feature I'd really like to see in Bitstring is support for Bigarray,
> since that avoids a copy into the OCaml heap and lets us do quite high
> performance parsing. If I remember right, there was a patch on the
> Bitstring issue tracker, but it wasn't parameterised (so it's either
> Bistring+string or Bitstring+bigarray, which isn't ideal).
Pardon my lack of familiarity with bigarrays, but I can't see what's the
difference between copying packets from pcap ring buffer into a bigarray
or into a string. Or do you mean using Bigarray.map_file on the whole
raw ring buffer and handle it without pcap help?
In my own experience, what slows down bitstring the most is the small
size of its internal buffers (128 bytes, ie. too small for many packet).
This simple change
(https://github.com/rixed/bitstring/commit/59076eb4c5ee1c8ed8648fc559c62e108b9c5037)
got me approx 20% improvement.
next prev parent reply other threads:[~2013-10-18 12:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 4:15 Johan Mazel
2013-10-18 5:33 ` Stéphane Glondu
2013-10-18 11:55 ` rixed
2013-10-18 11:59 ` Anil Madhavapeddy
2013-10-18 12:16 ` rixed [this message]
2013-10-18 12:20 ` Anil Madhavapeddy
2013-10-18 12:26 ` rixed
2013-10-18 13:52 ` Gerd Stolpmann
2013-10-18 14:13 ` rixed
2013-10-18 14:40 ` Stéphane Glondu
2013-10-18 14:20 ` Markus Mottl
2013-10-18 17:23 ` Paul Pelzl
2013-10-18 17:52 ` rixed
2013-10-18 20:09 ` Markus Mottl
2013-11-06 13:57 ` Richard W.M. Jones
2013-10-19 8:54 ` Johan Mazel
2013-10-21 7:58 ` rixed
2013-10-21 8:37 ` Johan Mazel
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=20131018121612.GB28679@ombreroze.happyleptic.org \
--to=rixed@happyleptic.org \
--cc=caml-list@inria.fr \
/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