All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: Al Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [git pull] vfs.git sysv pile
Date: Wed, 01 Mar 2023 14:21:56 +0100	[thread overview]
Message-ID: <8187743.T7Z3S40VBb@suse> (raw)
In-Reply-To: <20230301130018.yqds5yvqj7q26f7e@quack3>

On mercoledì 1 marzo 2023 14:00:18 CET Jan Kara wrote:
> On Wed 01-03-23 12:20:56, Fabio M. De Francesco wrote:
> > On venerdì 24 febbraio 2023 04:26:57 CET Al Viro wrote:
> > > 	Fabio's "switch to kmap_local_page()" patchset (originally after the
> > > 
> > > ext2 counterpart, with a lot of cleaning up done to it; as the matter of
> > > fact, ext2 side is in need of similar cleanups - calling conventions 
there
> > > are bloody awful).
> > 
> > If nobody else is already working on these cleanups in ext2 following your
> > suggestion, I'd be happy to work on this by the end of this week. I only
> > need
> > a confirmation because I'd hate to duplicate someone else work.
> > 
> > > Plus the equivalents of minix stuff...
> > 
> > I don't know this other filesystem but I could take a look and see whether
> > it
> > resembles somehow sysv and ext2 (if so, this work would be pretty simple
> > too,
> > thanks to your kind suggestions when I worked on sysv and ufs).
> > 
> > I'm adding Jan to the Cc list to hear whether he is aware of anybody else
> > working on this changes for ext2. I'm waiting for a reply from you (@Al) 
or
> > Jan to avoid duplication (as said above).
> 
> I'm not sure what exactly Al doesn't like about how ext2 handles pages and
> mapping but if you have some cleanups in mind, sure go ahead.

Hi Jan,

I might explain here and now what Al is referring to I'd prefer to show the 
code :-)

In brief I had made the conversions of fs/ufs and fs/sysv from kmap() to 
kmap_local_page() by porting what had been done for ext2. At that point Al 
suggested a much cleaner and elegant approach. 

Therefore, I threw away the port from ext2 and sent a series of 4 patches 
according to a long list of suggestions that Al kindly provided to me.

Now he is asking for somebody doing the same changes in ext2 too.

Thanks for the immediate reply.

Fabio   

> I don't have
> any plans on working on that code in the near term.
> 
> 								
Honza
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR





  reply	other threads:[~2023-03-01 13:22 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24  3:26 [git pull] vfs.git sysv pile Al Viro
2023-02-25  3:40 ` pr-tracker-bot
2023-03-01 11:20 ` Fabio M. De Francesco
2023-03-01 13:00   ` Jan Kara
2023-03-01 13:21     ` Fabio M. De Francesco [this message]
2023-03-01 14:14     ` Al Viro
2023-03-02  9:59       ` Jan Kara
2023-03-02 11:31         ` Fabio M. De Francesco
2023-03-02 19:35           ` Al Viro
2023-03-02 22:35             ` Al Viro
2023-03-03  5:10               ` Fabio M. De Francesco
2023-03-03  4:58             ` Fabio M. De Francesco
2023-03-08 17:40             ` Fabio M. De Francesco
2023-03-09 13:45               ` Fabio M. De Francesco
2023-03-02 19:26         ` Al Viro
2023-03-03  9:24           ` Jan Kara
2023-03-15 18:08       ` Fabio M. De Francesco
2023-03-16  9:00         ` Jan Kara
2023-03-16 10:30           ` Fabio M. De Francesco
2023-03-20 11:18             ` Fabio M. De Francesco
2023-03-20 12:47               ` Jan Kara
2023-03-27 10:29                 ` Fabio M. De Francesco
2023-05-25 20:10                   ` Jan Kara
2023-05-26 10:32                     ` Fabio M. De Francesco
2023-05-26 13:25                       ` Fabio M. De Francesco
2023-05-29  9:02                         ` Jan Kara

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=8187743.T7Z3S40VBb@suse \
    --to=fmdefrancesco@gmail.com \
    --cc=jack@suse.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.