mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steve Lord <lord@sgi.com>
To: Yaacov Akiba Slama <slamaya@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Announcing Journaled File System (JFS) release 1.0.0 available
Date: Thu, 28 Jun 2001 16:43:55 -0500	[thread overview]
Message-ID: <200106282143.f5SLht624150@jen.americas.sgi.com> (raw)
In-Reply-To: Message from Yaacov Akiba Slama <slamaya@yahoo.com>  of "Fri, 29 Jun 2001 00:12:50 +0300." <3B3B9DD2.1030103@yahoo.com>

> Hi,

> So I only hope that the smart guys at SGI find a way to prepare the 
> patches the way Linus loves because now the file 
> "patch-2.4.5-xfs-1.0.1-core" (which contains the modifs to the kernel 
> and not the new files) is about 174090 bytes which is a lot.
> 
> YA
> 

But that is not a patch intended for Linus, it is intended to enable all
the XFS features. I have a couple of kernel patches which total 46298 bytes
which get you a working XFS filesystem in the kernel, and I could do
lots of things to make them smaller. When you hit header files in the
correct manner for different platforms the size tends to mushroom.
These lines are all in different fcntl.h files for example:

+#define O_INVISIBLE    01000000 /* invisible I/O, for DMAPI/XDSM */
+#define O_INVISIBLE    0x80000 /* invisible I/O, for DMAPI/XDSM */
+#define O_INVISIBLE    02000000 /* invisible I/O, for DMAPI/XDSM */
+#define O_INVISIBLE    01000000 /* invisible I/O, for DMAPI/XDSM */
+#define O_INVISIBLE    01000000 /* invisible I/O, for DMAPI/XDSM */
+#define O_INVISIBLE    0x200000 /* invisible I/O, for DMAPI/XDSM */
+#define O_INVISIBLE    01000000 /* invisible I/O, for DMAPI/XDSM */
+#define O_INVISIBLE    0x200000 /* invisible I/O, for DMAPI/XDSM */
+#define O_INVISIBLE    01000000 /* invisible I/O, for DMAPI/XDSM */
+#define O_INVISIBLE    02000000 /* invisible I/O, for DMAPI/XDSM */
+#define O_INVISIBLE    0x80000 /* invisible I/O, for DMAPI/XDSM */
+#define O_INVISIBLE    02000000 /* invisible I/O, for DMAPI/XDSM */

You make the patches look a lot bigger than they really are. There is
a difference between a patch which is placing things in the correct
places and one which is designed to be as short as possible.

Steve




  parent reply	other threads:[~2001-06-28 21:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-28 21:12 Yaacov Akiba Slama
2001-06-28 21:21 ` Alan Cox
2001-06-28 21:43 ` Steve Lord [this message]
2001-06-29  4:53   ` Yaacov Akiba Slama
2001-06-28 23:08 ` Luigi Genoni
2001-06-28 23:23   ` james rich
2001-06-28 23:32     ` Luigi Genoni
  -- strict thread matches above, loose matches on Subject: below --
2001-06-29 13:01 Martin Knoblauch
2001-06-28 14:22 Steve Best
2001-06-28 15:52 ` Daniel Phillips
2001-06-28 22:52   ` Daniel Phillips
2001-06-28 16:02 ` Kervin Pierre
2001-06-29 13:33 ` Aaron Lehmann

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=200106282143.f5SLht624150@jen.americas.sgi.com \
    --to=lord@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=slamaya@yahoo.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®