From: Matthew Wilcox <willy@infradead.org>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: 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 14:03:16 -0800 [thread overview]
Message-ID: <20180131220316.GE28275@bombadil.infradead.org> (raw)
In-Reply-To: <CAN05THRVe30g9TG6UJF38q6d2s0jsiPU7MpPUy8zAgx_S3fQLA@mail.gmail.com>
On Thu, Feb 01, 2018 at 06:23:03AM +1000, ronnie sahlberg wrote:
> Compounding support for cifs.ko
>
> In CIFS.KO we are currently adding compounding support for SMB2/3.
> As SMB* is a very chatty protocol which likes to do open/query/close a LOT
> compounding support to wrap all three operations inside a single round trip
> can have a significant performance boost to meta data intensive workloads.
>
> In this talk I will talk about the challenges I faced and what previous design
> decisions in cifs.ko that made this very hard and how I refactored the design.
>
> I will also talk about the current status of these patches as well as give a
> live demonstration of compounding in action.
I think all of these things are worthwhile and stand to improve
the implementation a lot. Are they of interest to other filesystem
developers? Are there VFS changes which would help make compounding
easier? Or is this only of interest to other CIFS people, in which case
this might not be the best use of a slot at LSFMM ...
next prev parent reply other threads:[~2018-01-31 22:03 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 [this message]
2018-01-31 22:13 ` Chuck Lever
2018-01-31 22:22 ` ronnie sahlberg
2018-02-01 2:40 ` J. Bruce Fields
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=20180131220316.GE28275@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=ronniesahlberg@gmail.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).