v9fs.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Eric Van Hensbergen <ericvh@kernel.org>
To: torvalds@linux-foundation.org
Cc: v9fs@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [GIT PULL] fs/9p patches for 6.9 merge window
Date: Fri, 15 Mar 2024 15:10:03 +0000	[thread overview]
Message-ID: <ZfRkyxUf8TIgsYjA@1149290c588b> (raw)

[-- Attachment #1: Type: text/plain, Size: 2117 bytes --]

The following changes since commit 6613476e225e090cc9aad49be7fa504e290dd33d:

  Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/ericvh/v9fs.git tags/9p-for-6.9

for you to fetch changes up to be57855f505003c5cafff40338d5d0f23b00ba4d:

  fs/9p: fix dups even in uncached mode (2024-01-26 16:46:56 +0000)

----------------------------------------------------------------
fs/9p changes for the 6.9 merge window

This pull request includes a number of patches
addressing improvements in the cache portions of the 9p
client.

The biggest improvements have to do with fixing handling
of inodes and eliminating duplicate structures and unnecessary
allocation/release of inode structures and many associated
unnecessary protocol traffic.  This also dramatically
reduced code complexity across the code and sets us up to add
proper temporal cache capabilities.

Signed-off-by: Eric Van Hensbergen <ericvh@kernel.org>

----------------------------------------------------------------
Eric Van Hensbergen (8):
      fs/9p: switch vfsmount to use v9fs_get_new_inode
      fs/9p: convert mkdir to use get_new_inode
      fs/9p: remove walk and inode allocation from symlink
      fs/9p: Eliminate redundant non-cache path in mknod
      fs/9p: Eliminate now unused v9fs_get_inode
      fs/9p: rework qid2ino logic
      fs/9p: simplify iget to remove unnecessary paths
      fs/9p: fix dups even in uncached mode

 fs/9p/v9fs.h           |  31 +++++-----------------------
 fs/9p/v9fs_vfs.h       |  11 ++++++----
 fs/9p/vfs_dir.c        |   4 ++--
 fs/9p/vfs_inode.c      | 150 +++++++++++++++++++--------------------------------------------------------------------------------------------------------------------
 fs/9p/vfs_inode_dotl.c | 194 ++++++++++++++++++++++++++++++++-----------------------------------------------------------------------------------------------------------------------------------------------
 fs/9p/vfs_super.c      |  45 +----------------------------------------
 6 files changed, 71 insertions(+), 364 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2024-03-15 15:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15 15:10 Eric Van Hensbergen [this message]
2024-03-15 17:17 ` [GIT PULL] fs/9p patches for 6.9 merge window Linus Torvalds
2024-03-15 17:20 ` pr-tracker-bot
2024-04-08 14:14 ` Oleg Nesterov
2024-04-10 17:20   ` Eric Van Hensbergen
2024-04-10 18:57     ` Eric Van Hensbergen
2024-04-11  9:29       ` Oleg Nesterov

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=ZfRkyxUf8TIgsYjA@1149290c588b \
    --to=ericvh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=v9fs@lists.linux.dev \
    /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).