From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] From our "not quite grasping the concept" file
Date: Thu, 8 Nov 2007 11:38:15 -0500 [thread overview]
Message-ID: <cc1bc25a8840bebe37f441f0be1216b9@coraid.com> (raw)
In-Reply-To: <6FACD1A6-936C-4B91-9314-1BF3D7C7A0D0@lanl.gov>
> That's one of the options. We are probably going to start with
> serialized content (no copying of the data though) and if it is too
> slow, we won't do serialization.
i'm not sure i understand. either the message is formatted (and the data
copied) or it's not. i must be missing something.
- erik
next prev parent reply other threads:[~2007-11-08 16:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-08 7:31 ron minnich
2007-11-08 12:00 ` Richard Miller
2007-11-08 12:55 ` Eric Van Hensbergen
2007-11-08 15:20 ` erik quanstrom
2007-11-08 16:07 ` Latchesar Ionkov
2007-11-08 16:38 ` erik quanstrom [this message]
2007-11-08 17:24 ` Latchesar Ionkov
2007-11-08 16:10 ` Eric Van Hensbergen
2007-11-08 16:33 ` erik quanstrom
2007-11-08 16:42 ` ron minnich
2007-11-08 16:51 ` roger peppe
2007-11-08 13:57 ` erik quanstrom
2007-11-08 19:46 ` Pietro Gagliardi
2007-11-09 1:07 ` dave.l
2007-11-09 4:43 ` Paul Lalonde
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=cc1bc25a8840bebe37f441f0be1216b9@coraid.com \
--to=quanstro@coraid.com \
--cc=9fans@cse.psu.edu \
/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).