mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Brandenburg <martin@omnibond.com>
To: hubcap@omnibond.com, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, devel@lists.orangefs.org
Cc: Martin Brandenburg <martin@omnibond.com>
Subject: [PATCH 0/7] orangefs uapi
Date: Fri, 26 Jan 2018 14:07:10 -0500	[thread overview]
Message-ID: <20180126190717.11075-1-martin@omnibond.com> (raw)

First delete a good bit of dead code and change a few things to static.

Then move userspace visible interface to uapi.

This isn't immediately helpful without userspace consumers.  This should
be helpful to your [Mike's] work with OrangeFS 3.0.  We will need to
translate between OrangeFS internal data structures and kernel interface
data structures in the pvfs2-client-core.

I have also written a "fakecore" which does about the bare minimum to
start up and respond to mount requests.  I intend to use this as a
vehicle for experimentation with fuzzing and testing performance through
our kernel code without the rest of OrangeFS running.

We'll want to consider whether any names in here should be changed
before setting this in stone.  Most start with orangefs but there's a
few outliers.  Particularly struct ORANGEFS_sys_attr_s contains some
fields which the kernel doesn't need to know.

Martin Brandenburg (7):
  orangefs: make orangefs_client_debug_init static
  orangefs: remove gossip_ldebug and gossip_lerr
  orangefs: remove ORANGEFS_KERNEL_DEBUG
  orangefs: make orangefs_make_bad_inode static
  ornagefs: make several *_operations structs static
  orangefs: remove unused code
  orangefs: create uapi interface

 fs/orangefs/acl.c                |   1 -
 fs/orangefs/dcache.c             |   1 -
 fs/orangefs/devorangefs-req.c    |  54 ++-
 fs/orangefs/dir.c                |   1 -
 fs/orangefs/downcall.h           | 137 --------
 fs/orangefs/file.c               |   1 -
 fs/orangefs/inode.c              |   5 +-
 fs/orangefs/namei.c              |   1 -
 fs/orangefs/orangefs-bufmap.c    |   1 -
 fs/orangefs/orangefs-cache.c     |   1 -
 fs/orangefs/orangefs-debug.h     |  33 --
 fs/orangefs/orangefs-debugfs.c   |   8 +-
 fs/orangefs/orangefs-debugfs.h   |   1 -
 fs/orangefs/orangefs-dev-proto.h |  61 ----
 fs/orangefs/orangefs-kernel.h    |  93 +----
 fs/orangefs/orangefs-mod.c       |   1 -
 fs/orangefs/orangefs-sysfs.c     |   1 -
 fs/orangefs/orangefs-utils.c     |  40 +--
 fs/orangefs/protocol.h           | 354 -------------------
 fs/orangefs/super.c              |   3 +-
 fs/orangefs/symlink.c            |   1 -
 fs/orangefs/upcall.h             | 260 --------------
 fs/orangefs/waitqueue.c          |   1 -
 fs/orangefs/xattr.c              |   1 -
 include/uapi/linux/orangefs.h    | 732 +++++++++++++++++++++++++++++++++++++++
 25 files changed, 788 insertions(+), 1005 deletions(-)
 delete mode 100644 fs/orangefs/downcall.h
 delete mode 100644 fs/orangefs/orangefs-dev-proto.h
 delete mode 100644 fs/orangefs/upcall.h
 create mode 100644 include/uapi/linux/orangefs.h

-- 
2.14.2

             reply	other threads:[~2018-01-26 19:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-26 19:07 Martin Brandenburg [this message]
2018-01-26 19:07 ` [PATCH 1/7] orangefs: make orangefs_client_debug_init static Martin Brandenburg
2018-01-26 19:07 ` [PATCH 2/7] orangefs: remove gossip_ldebug and gossip_lerr Martin Brandenburg
2018-01-26 19:07 ` [PATCH 3/7] orangefs: remove ORANGEFS_KERNEL_DEBUG Martin Brandenburg
2018-01-26 19:07 ` [PATCH 4/7] orangefs: make orangefs_make_bad_inode static Martin Brandenburg
2018-01-26 19:07 ` [PATCH 5/7] ornagefs: make several *_operations structs static Martin Brandenburg
2018-01-26 19:07 ` [PATCH 6/7] orangefs: remove unused code Martin Brandenburg
2018-01-26 19:07 ` [PATCH 7/7] orangefs: create uapi interface Martin Brandenburg
2018-01-26 19:15 ` [PATCH 0/7] orangefs uapi martin

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=20180126190717.11075-1-martin@omnibond.com \
    --to=martin@omnibond.com \
    --cc=devel@lists.orangefs.org \
    --cc=hubcap@omnibond.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®