caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
To: "caml" <caml-list@inria.fr>
Subject: RE: [Caml-list] Wish List for Large Mutable Objects
Date: Sun, 1 Aug 2004 22:14:15 -0700	[thread overview]
Message-ID: <OOEALCJCKEBJBIJHCNJDGEPPHFAB.vanevery@indiegamedesign.com> (raw)
In-Reply-To: <004301c47841$561ff9c0$0201a8c0@dylan>

David McClain wrote:
>
> How is it you claim to speak for my C++ manager about scatter
> gather?

I used to write 3d device drivers for a living.  I was never much for
the 'nasty innards' of OS internals, preferring to concentrate on ASM
loop optimizations for 3d graphics.  That said, Scatter-Gather DMA is
generally a property of a memory controller, i.e. a chipset on a
motherboard.  I seriously doubt you have user mode access to such memory
controllers.  If you do, point me at the API for it.  I'm happy to stand
corrected, but as far as I know, scatter-gather DMA is kernel mode stuff
on all common architectures.

There is the outside possibility that you mean something different by
'scatter-gather' than a device driver writer means by 'scatter-gather'.
A similar loggerhead to what an 'array' is.

A third possibility is you have written a library that assumes
scatter-gather DMA is happening under the hood somehow, but doesn't
explicitly control it in any way.  To which I say, memory controllers
are different.  In the absence of a query interface to determine their
capabilities, I don't see how you'd rigorously control algorithmic
performance.  Maybe you do not regard rigor as so important - memory
cache hierarchies sorta work without anyone doing anything explicit,
after all.  But I would say, without rigor, you probably won't end up
with anything.  Just an idea that something should be fast under some
circumstances, rather than any proven, repeatable reality.

For clarity, these aren't personal comments.  This is just my
understanding of scatter-gather DMA vs. whatever your understanding is.


Cheers,                         www.indiegamedesign.com
Brand*n Van Every               S*attle, WA

Praise Be to the caml-list Bayesian filter! It blesseth
my postings, it is evil crap!  evil crap!  Bigarray!
Unboxed overhead group!  Wondering!  chant chant chant...

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2004-08-02  5:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-31 18:29 David McClain
2004-08-01  3:36 ` Brandon J. Van Every
2004-08-02  5:28   ` Brandon J. Van Every
2004-08-01  4:06 ` Brandon J. Van Every
2004-08-02  2:38   ` David McClain
2004-08-02  3:20     ` Brandon J. Van Every
2004-08-02  3:32       ` David McClain
2004-08-02  5:14         ` Brandon J. Van Every [this message]
2004-08-02  8:00           ` Ville-Pertti Keinonen
2004-08-02  9:12             ` David McClain
2004-08-04  7:24     ` Alex Baretta

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=OOEALCJCKEBJBIJHCNJDGEPPHFAB.vanevery@indiegamedesign.com \
    --to=vanevery@indiegamedesign.com \
    --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;
as well as URLs for NNTP newsgroup(s).