From: "Nitin Gupta" <nitingupta910@gmail.com>
To: "Michael-Luke Jones" <mlj28@cam.ac.uk>
Cc: lkml <linux-kernel@vger.kernel.org>,
linux-mm-cc@laptop.org,
linuxcompressed-devel@lists.sourceforge.net,
"Andrew Morton" <akpm@linux-foundation.org>,
"Richard Purdie" <richard@openedhand.com>,
"Daniel Hazelton" <dhazelton@enter.net>,
"Bret Towe" <magnade@gmail.com>,
"Satyam Sharma" <satyam.sharma@gmail.com>
Subject: Re: [RFC] LZO de/compression support - take 5
Date: Mon, 28 May 2007 17:39:22 +0530 [thread overview]
Message-ID: <4cefeab80705280509x73c8a1c9m9e8ba58d235a3666@mail.gmail.com> (raw)
In-Reply-To: <871A3BF3-A0EA-40E4-AB5F-FF6DDCE12DC7@cam.ac.uk>
On 5/28/07, Michael-Luke Jones <mlj28@cam.ac.uk> wrote:
> On 28 May 2007, at 07:59, Nitin Gupta wrote:
>
> > If we get no perf. problems with this patch, then I beleive it is now
> > suitable to inclusion in mainline. Further cleanups and optimizations
> > can surely be done after that. It's still just ~500 LOC.
>
> Before LZO code is sent to Linus, its selection in Kconfig should be
> made orthogonal to the current zlib selection code.
>
> This means:
> 1) Options in lib/Kconfig hidden (selectable by drivers as required)
LZO as hidden option has no practical sense. Although LZO should be
auto-selected when some dependent project is selected (e.g. reieser4)
- there should be separate patch for this. Mixing such changes with
'core' LZO patch will just add side noise.
> 2) Decompression and Compression support separated, as read-only
> filesystems only need to build in decompression support.
>
Ok, I will do this. I wonder if some difference in opinion in such
things can actually cause 10+ extra RFCs?
Cheers,
Nitin
next prev parent reply other threads:[~2007-05-28 12:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-28 6:59 Nitin Gupta
2007-05-28 9:44 ` Satyam Sharma
2007-05-28 10:49 ` Michael-Luke Jones
2007-05-28 12:09 ` Nitin Gupta [this message]
2007-05-28 12:16 ` Michael-Luke Jones
2007-05-28 13:47 ` Pekka Enberg
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=4cefeab80705280509x73c8a1c9m9e8ba58d235a3666@mail.gmail.com \
--to=nitingupta910@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dhazelton@enter.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm-cc@laptop.org \
--cc=linuxcompressed-devel@lists.sourceforge.net \
--cc=magnade@gmail.com \
--cc=mlj28@cam.ac.uk \
--cc=richard@openedhand.com \
--cc=satyam.sharma@gmail.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
all inboxes | Powered by JetHome®