linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Suparna Bhattacharya <suparna@in.ibm.com>
Cc: cotte@freenet.de, linux-kernel@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, schwidefsky@de.ibm.com,
	akpm@osdl.org, Christoph Hellwig <hch@infradead.org>
Subject: Re: [RFC/PATCH 2/4] fs/mm: execute in place (3rd version)
Date: Tue, 24 May 2005 12:28:40 +0200	[thread overview]
Message-ID: <20050524102839.GA17254@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20050524093029.GA4390@in.ibm.com>

On Tue, 24 May 2005 15:00:29 +0530, Suparna Bhattacharya wrote:
> 
> OK, though this leaves filemap.c alone which is good, I have to admit
> that this entire duplication of read/write routines really worries me.
> 
> There has to be a third way.

There is.  I'm not convinced it's a good idea, but maybe someone
smarter can comment on it.

v1 and v2 basically contained the generic code with an extra check
here and there.

int do_shtuff(...)
{
	if (xip)
		do_xip_shtuff(...);
	/* shtuff */
	...
}

v3 contains a copy of the generic code in filemap_xip.c.

int do_shtuff_xip(...)
{
	do_xip_shtuff(...);
	/* shtuff copied from filemap.c */
	...
}

v4 could do something like this:

int __do_generic_shtuff(...)
{
	/* the generic shtuff */
	...
}

int do_shtuff(...)
{
	return __do_generic_shtuff(...);
}

int do_shtuff_xip(...)
{
	do_xip_shtuff(...);
	return __do_generic_shtuff(...);
}

Jörn

-- 
You cannot suppose that Moliere ever troubled himself to be original in the
matter of ideas. You cannot suppose that the stories he tells in his plays
have never been told before. They were culled, as you very well know.
-- Andre-Louis Moreau in Scarabouche
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2005-05-24 10:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1116866094.12153.12.camel@cotte.boeblingen.de.ibm.com>
2005-05-23 17:30 ` [RFC/PATCH 2/4] fs/mm: execute in place (3rd version) Carsten Otte
2005-05-24  9:30   ` Suparna Bhattacharya
2005-05-24 10:28     ` Jörn Engel [this message]
2005-05-24 11:09     ` Carsten Otte
2005-05-24 13:32       ` Suparna Bhattacharya
2005-05-24 14:34         ` Carsten Otte
2005-05-25 17:51           ` Badari Pulavarty
2005-05-26 13:22             ` Suparna Bhattacharya
2005-05-26 13:19               ` Carsten Otte
2005-05-26 16:43                 ` Badari Pulavarty
2005-05-26 13:29             ` Carsten Otte
2005-05-28  9:05             ` Christoph Hellwig
2005-05-24 17:01     ` Carsten Otte
2005-05-28  9:08       ` Christoph Hellwig
2005-05-23 17:30 ` [RFC/PATCH 3/4] ext2: " Carsten Otte
2005-05-23 17:30 ` [RFC/PATCH 4/4] madvice/fadvice: " Carsten Otte

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=20050524102839.GA17254@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=akpm@osdl.org \
    --cc=cotte@freenet.de \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=suparna@in.ibm.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).