From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Michael Tokarev <mjt@tls.msk.ru>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, Ian Kent <raven@themaw.net>,
Thomas Meyer <thomas@m3y3r.de>,
autofs@vger.kernel.org
Subject: Re: autofs: make the autofsv5 packet file descriptor use a packetized pipe
Date: Mon, 30 Apr 2012 13:03:01 -0700 [thread overview]
Message-ID: <4F9EEFF5.4000703@zytor.com> (raw)
In-Reply-To: <4F9DDD3E.6010801@zytor.com>
On 04/29/2012 05:30 PM, H. Peter Anvin wrote:
> Incidentally, I think there is a good reason to add a v6 packet type
> regardless, for efficiency: with packetized pipes there really is no
> point in sending a packet which is mostly padding for no good reason.
Thinking about it some more: for v6, I wouldn't use a packetized pipe at
all (due to the unnecessary extra buffer consumption.) Instead just put
the message size in the header and read a large chunk, which may end up
being more than one packet and may end up with a partial packet at the
end. *This is okay*, because there is only one reader, and any
additional data needed will be gotten the next time around the loop.
-hpa
next prev parent reply other threads:[~2012-04-30 20:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120429205429.63CCD7C0064@ra.kernel.org>
2012-04-30 0:15 ` autofs: make the autofsv5 packet file descriptor use a packetized pipe H. Peter Anvin
2012-04-30 0:25 ` Linus Torvalds
2012-04-30 0:28 ` H. Peter Anvin
2012-04-30 0:33 ` Linus Torvalds
2012-04-30 0:35 ` H. Peter Anvin
2012-04-30 0:43 ` Linus Torvalds
2012-04-30 0:45 ` H. Peter Anvin
2012-04-30 1:29 ` Ian Kent
2012-04-30 1:56 ` Linus Torvalds
2012-04-30 5:57 ` Ian Kent
2012-04-30 0:30 ` H. Peter Anvin
2012-04-30 0:37 ` Linus Torvalds
2012-04-30 20:03 ` H. Peter Anvin [this message]
2012-04-30 20:11 ` Linus Torvalds
2012-04-30 20:14 ` H. Peter Anvin
2012-04-30 6:27 ` Michael Tokarev
2012-04-30 6:43 ` Michael Tokarev
2012-04-30 6:48 ` H. Peter Anvin
2012-04-30 6:55 ` Ian Kent
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=4F9EEFF5.4000703@zytor.com \
--to=hpa@zytor.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=autofs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=raven@themaw.net \
--cc=thomas@m3y3r.de \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.