From: Bill Zissimopoulos <billziss@navimatics.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: FUSE for Cygwin
Date: Sun, 19 Jun 2016 20:32:00 -0000 [thread overview]
Message-ID: <D38C3759.9411%billziss@navimatics.com> (raw)
In-Reply-To: <57667FEF.5070801@gmx.de>
On 6/19/16, 4:20 AM, "cygwin-owner@cygwin.com on behalf of Herbert
Stocker" <cygwin-owner@cygwin.com on behalf of hersto@gmx.de> wrote:
>What i don't like on (3) is that when a Cygwin process accesses the
>FUSE file system there are two Cygwin processes whose communication
>is translated from Posix to Win32 and then back (which is done again
>for the response).
[snip]
>A) Besides the double double translations of every request, there
> is also the need for four Kernel/Usermode transitions, which take
> their time.
By the way Herbert in re-reading your email, you may *not* have meant to
say that in the current WinFsp/FUSE scheme there are 4 *context switches*
(instead of 2), in which case my apologies for trying to explain something
you already were aware of.
Bill
next prev parent reply other threads:[~2016-06-19 18:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 8:02 Bill Zissimopoulos
2016-06-19 18:53 ` Herbert Stocker
2016-06-19 19:30 ` Bill Zissimopoulos
2016-06-20 0:29 ` Herbert Stocker
2016-06-22 21:01 ` Bill Zissimopoulos
2016-06-22 21:21 ` Jeffrey Altman
2016-06-22 23:11 ` Bill Zissimopoulos
2016-06-19 20:32 ` Bill Zissimopoulos [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-06-17 8:42 FUSE for Cygwin - was: Re: Fork and Windows Heap Bill Zissimopoulos
2016-06-17 18:55 ` FUSE for Cygwin Herbert Stocker
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=D38C3759.9411%billziss@navimatics.com \
--to=billziss@navimatics.com \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).