From: "Harrosh, Boaz" <Boaz.Harrosh@netapp.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] ZUFS - Zero Copy User-Mode FileSystem - One year Later
Date: Wed, 3 Oct 2018 12:46:52 +0000 [thread overview]
Message-ID: <MWHPR06MB28965FBD1C86181DD7986C9FEEE90@MWHPR06MB2896.namprd06.prod.outlook.com> (raw)
In-Reply-To: <20181003110644.GA12451@kroah.com>
Greg KH <gregkh@linuxfoundation.org> Wrote:
>> On Wed, Oct 03, 2018 at 09:35:54AM +0000, Harrosh, Boaz wrote:
>> Linux Plumbers 2018: ZUFS - Zero Copy User-Mode FileSystem - One year Later
<snap>
> Why wouldn't this be better discussed at the file-system-specific
> conference? Or have you already done that this year?
>
> thanks,
> greg k-h
Yes I have presented at LSF. It was a full discussion. And, 6 month ago, was
very not ready for upstream at that time.
Last plumbers my talk raised a lot of interest, was then at the POC stage.
I would like to present the current status, when code is much more complete
and actually ready for clients computers in stability and fixture set.
And try to draw in more community interest and participation. In what I believe
is a very Interesting project. Some of the Technics I present are beyond pure FS
and demonstrate a new way to communicate with user-mode servers, taking into
account cpu-locality and NUMA awareness.
[That said it is all about me sleeping on guard and submitting a plumbers talk proposal
to late. So it was suggested I might ask about a Kernel track
]
Thanks
Boaz
next prev parent reply other threads:[~2018-10-03 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 9:35 Harrosh, Boaz
2018-10-03 11:06 ` Greg KH
2018-10-03 12:46 ` Harrosh, Boaz [this message]
2018-10-08 7:46 ` Boaz Harrosh
2018-10-08 13:47 ` Greg KH
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=MWHPR06MB28965FBD1C86181DD7986C9FEEE90@MWHPR06MB2896.namprd06.prod.outlook.com \
--to=boaz.harrosh@netapp.com \
--cc=gregkh@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.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