From: beto@ncube.com beto@ncube.com
Subject: [9fans] convS2M improvement
Date: Fri, 24 Oct 1997 11:02:52 -0700 [thread overview]
Message-ID: <19971024180252.KsdQxfSG9CT2ozkNSV_VfisM7gQjS8eaQh9oO4ct2rA@z> (raw)
Hi,
I've modified convS2M to avoid having to copy the
data during a read reply. The idea is to set the Fcall data
pointer to point to the right place within the
reply message.
ConvS2M starts doing it's data conversion and if the data
pointer is already pointing to the right place it bypasses
the copy.
case Rread:
SHORT(fid);
SHORT(count);
p++; /* pad(1) */
if (p != (uchar*)f->data) {
STRING(data, f->count);
} else
p+=f->count;
break;
The server needs to know the data offset for a read reply,
but some macro definitions will solve the problem.
p->reply.data = (char *) p->rbp->wptr+8;
With this enhancement a 9P server does not have to copy
data for reads.
Has something like this been done to brazil/plan9?
P.S.
This is not scatter/gatther but it's so simple :-)
reply other threads:[~1997-10-24 18:02 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=19971024180252.KsdQxfSG9CT2ozkNSV_VfisM7gQjS8eaQh9oO4ct2rA@z \
--to=beto@ncube.com \
/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).