public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: arjan@infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 0/4] Series to allow a "const" file_operations struct
Date: Fri, 6 Jan 2006 16:29:13 -0800	[thread overview]
Message-ID: <20060106162913.7621895c.akpm@osdl.org> (raw)
In-Reply-To: <43BEF338.3010403@cosmosbay.com>

Eric Dumazet <dada1@cosmosbay.com> wrote:
>
> Arjan van de Ven a écrit :
> > On Fri, 2006-01-06 at 22:45 +0100, Arjan van de Ven wrote:
> >> Hi,
> >>
> >> this series allows drivers to have "const" file_operations, by making
> >> the f_ops field in the inode const. This has another benefit, there have
> > 
> > ok there was a sentence missing here. The first benefit is that this
> > moves these hot datastructures to the rodata section, which means they
> > won't accidentally be doing false cacheline sharing.
> > 
> 
> Definitly a good thing I agree.
> 
> But your patches miss to really declare all 'struct file_operations' as const, 
> dont they ?
> 
> 
> On my x86_64 machine, I managed to reduce by 10% .data section by moving all 
> file_operations, but also 'address_space_operations', 'inode_operations, 
> super_operations, dentry_operations, seq_operations, ... to rodata section.
> 
> size vmlinux*
>     text    data     bss     dec     hex filename
> 2476156  522236  244868 3243260  317cfc vmlinux
> 2588685  571348  246692 3406725  33fb85 vmlinux.old
> 

Confused.   Why should this result in an aggregate reduction in vmlinux size?

  reply	other threads:[~2006-01-07  0:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-06 21:45 [patch 0/4] Series to allow a "const" file_operations struct Arjan van de Ven
2006-01-06 21:46 ` [patch 1/4] fix some f_ops abuse in acpi Arjan van de Ven
2006-01-06 21:47 ` [patch 2/4] fix input layer f_ops abuse Arjan van de Ven
2006-01-06 23:12   ` Dmitry Torokhov
2006-01-06 21:49 ` [patch 3/4] fix cifs bugs wrt writing to f_ops Arjan van de Ven
2006-01-06 21:51 ` [patch 4/4] Actually make the f_ops field const Arjan van de Ven
2006-01-07  8:00   ` Andrew Morton
2006-01-07  8:13     ` Arjan van de Ven
2006-01-06 21:55 ` [patch 0/4] Series to allow a "const" file_operations struct Arjan van de Ven
2006-01-06 22:46   ` Eric Dumazet
2006-01-07  0:29     ` Andrew Morton [this message]
2006-01-07  1:01       ` Arnd Bergmann
2006-01-07  7:40       ` Eric Dumazet
2006-01-07  8:33       ` Arjan van de Ven

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=20060106162913.7621895c.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=dada1@cosmosbay.com \
    --cc=linux-kernel@vger.kernel.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