From: bfields@fieldses.org (J. Bruce Fields)
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: Chuck Lever <chuck.lever@oracle.com>,
Matthew Wilcox <willy@infradead.org>,
lsf-pc@lists.linux-foundation.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [LSF/MM TOPIC] Compounding support in CIFS.KO
Date: Wed, 31 Jan 2018 21:40:05 -0500 [thread overview]
Message-ID: <20180201024005.GE3814@fieldses.org> (raw)
In-Reply-To: <CAN05THS3tGUY=ncrAoB+9yt=rPQJy4Zrb_1FvA=fK3q-pwNMdg@mail.gmail.com>
On Thu, Feb 01, 2018 at 08:22:03AM +1000, ronnie sahlberg wrote:
> I think you are right. The topic of cifs compounding is only really
> interesting to cifs folks and not many others. While other
> filesystems such as NFSv4 has compounding too, the way compounding
> works in cifs is different enough that there is little meaningful
> overlap between the two.
I'm trying to remember what people have found to be the obstacles to
more aggressive use of compounds in NFS. (Things like opening a file
and doing IO to it in one compound.) Might it be more practical with
some VFS changes? Are there some shared CIFS/NFS issues there?
Anyway, the hallway track is fine....
--b.
next prev parent reply other threads:[~2018-02-01 2:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 20:23 [LSF/MM TOPIC] Compounding support in CIFS.KO ronnie sahlberg
2018-01-31 22:03 ` Matthew Wilcox
2018-01-31 22:13 ` Chuck Lever
2018-01-31 22:22 ` ronnie sahlberg
2018-02-01 2:40 ` J. Bruce Fields [this message]
2018-02-01 4:31 ` Steve French
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=20180201024005.GE3814@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=ronniesahlberg@gmail.com \
--cc=willy@infradead.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 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).