mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Robert Love <rml@novell.com>
Cc: mpm@selenic.com, ttb@tentacle.dhs.org, akpm@osdl.org,
	linux-kernel@vger.kernel.org, gamin-list@gnome.org
Subject: Re: [patch] make dnotify compile-time configurable
Date: Fri, 1 Oct 2004 08:31:10 -0700	[thread overview]
Message-ID: <20041001083110.76a58fd2.rddunlap@osdl.org> (raw)
In-Reply-To: <1096644076.7676.6.camel@betsy.boston.ximian.com>

On Fri, 01 Oct 2004 11:21:16 -0400 Robert Love wrote:

| On Fri, 2004-10-01 at 10:11 -0500, Matt Mackall wrote:
| 
| > Indeed, it's been useful for months. Unfortunately my development
| > boxes are still mothballed so progress upstream is stalled.
| 
| Oh, great...
| 
| /me finds your broken out patches ...
| 
| Ah, you ifdef'ed out the dnotify variables in the inode structure.  That
| was the original reason I did this--doh.
| 
| In mine, I remove the sysctl entirely, which you don't.  I also add some
| documentation to dnotify.txt.  Not a big difference.
| 
| > > Disabling CONFIG_DNOTIFY saves a couple hundred bytes off of vmlinux.
| > 
| > Hmm, thought I saved at least 1 or 2k.
| 
| I thought my number sounded suspect.  Dunno.
| 
| Here is a respun patch ifdef'ing out the dnotify member variables in
| struct inode.  This one is diff'ed against my inode tree since the
| struct inode changes break one path or the other and, well, I like to
| mix things up.
| 
| John, want to merge this into the inotify patch?

I'd rather see inotify additions and dnotify config options kept
separate.  They may serve a similar purpose, but inotify doesn't
replace the dnotify API.  If the latter were true, combining
them would make sense IMO.


| Thanks, Matt.


-- 
~Randy

  reply	other threads:[~2004-10-01 15:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-01  6:24 Robert Love
2004-10-01 15:11 ` Matt Mackall
2004-10-01 15:21   ` Robert Love
2004-10-01 15:31     ` Randy.Dunlap [this message]
2004-10-01 15:44       ` Robert Love
2004-10-01 15:58         ` Randy.Dunlap
2004-10-01 17:01           ` Robert Love
2004-10-01 17:27             ` Matt Mackall
2004-10-01 17:30               ` Robert Love
2004-10-01 17:30                 ` Randy.Dunlap
2004-10-01 17:37                   ` Robert Love
2004-10-01 17:38                     ` Randy.Dunlap

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=20041001083110.76a58fd2.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=akpm@osdl.org \
    --cc=gamin-list@gnome.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpm@selenic.com \
    --cc=rml@novell.com \
    --cc=ttb@tentacle.dhs.org \
    /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

Powered by JetHome