From: "Peter J. Braam" <braam@clusterfilesystem.com>
To: tux-list@redhat.com, intermezzo-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: large & fragmented TUX requests
Date: Thu, 2 Aug 2001 16:12:14 -0600 [thread overview]
Message-ID: <20010802161214.E1498@lustre.clusterfilesystem.com> (raw)
Hi,
I am working on a protocol handler for InterMezzo. This is a kernel
level protocol handler than can unpack DAFS style packets and service
the requests.
I have two basic questions about the code (looking at 2.4.6-3.1)
1) input.c
If a request arrives in multiple pieces, req->proto->parse_message
returns 0 and read_request is called multiple times. Why is read
request not overwriting data that was already received?
2) large requests
Some of the RPC's I want to handle are for receiving file data. Would
it make sense when it is known that a large page aligned buffer with
file data is coming, to simply allocate buffers of the right size (say
up to 64K max) and point req->req_headers at it?
In that way I can read the chunk in and later map the pages into a
file to get it to disk.
There is no standard "recv_file" (ala sendfile) api, right?
Thanks for pointers and thoughts.
- Peter -
next reply other threads:[~2001-08-02 22:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-02 22:12 Peter J. Braam [this message]
2001-08-21 13:14 ` Ingo Molnar
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=20010802161214.E1498@lustre.clusterfilesystem.com \
--to=braam@clusterfilesystem.com \
--cc=intermezzo-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tux-list@redhat.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
all inboxes | Powered by JetHome®