linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: Brent Casavant <bcasavan@sgi.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>, Andi Kleen <ak@suse.de>,
	"Adam J. Richter" <adam@yggdrasil.com>,
	colpatch@us.ibm.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH] Use MPOL_INTERLEAVE for tmpfs files
Date: Wed, 10 Nov 2004 14:20:42 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0411101406360.2806-100000@localhost.localdomain> (raw)
In-Reply-To: <Pine.SGI.4.58.0411092020550.101942@kzerza.americas.sgi.com>

On Tue, 9 Nov 2004, Brent Casavant wrote:
> On Tue, 9 Nov 2004, Hugh Dickins wrote:
> 
> > Doesn't quite play right with what was my "NULL sbinfo" convention.
> 
> Howso?  I thought it played quite nicely with it.  We've been using
> NULL sbinfo as an indicator that an inode is from tmpfs rather than
> from SysV or /dev/zero.  Or at least that's the way my brain was
> wrapped around it.

That was the case you cared about, but remember I extended yours so
that tmpfs mounts could also suppress limiting, and get NULL sbinfo.

> The NULL sbinfo scheme worked perfectly for me, with very little hassle.

Yes, it would have worked just right for the important cases.

> > but they're two hints that I should rework that to get out of people's
> > way.  I'll do a patch for that, then another something like yours on
> > top, for you to go back and check.
> 
> Is this something imminent, or on the "someday" queue?  Just asking
> because I'd like to avoid doing additional work that might get thrown
> away soon.

I understand your concern ;)  I'm working on it, today or tomorrow.

> > I'm irritated to realize that we can't change the default for SysV
> > shared memory or /dev/zero this way, because that mount is internal.
> 
> Well, the only thing preventing this is that I stuck the flag into
> sbinfo, since it's an filesystem-wide setting.  I don't see any reason
> we couldn't add a new flag in the inode info flag field instead.  I
> think there would also be some work to set pvma.vm_end more precisely
> (in mpol_shared_policy_init()) in the SysV case.

It's not a matter of where to store the info, it's that we don't have
a user interface for remounting something that's not mounted anywhere.

Hugh

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2004-11-10 14:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-02  1:07 Brent Casavant
2004-11-02  1:43 ` Dave Hansen
2004-11-02  9:13 ` Andi Kleen
2004-11-02 15:46 ` Martin J. Bligh
2004-11-02 15:55   ` Andi Kleen
2004-11-02 16:55     ` Martin J. Bligh
2004-11-02 22:17       ` Brent Casavant
2004-11-02 22:51         ` Martin J. Bligh
2004-11-03  1:12           ` Brent Casavant
2004-11-03  1:30             ` Martin J. Bligh
2004-11-03  8:44           ` Hugh Dickins
2004-11-03  9:01             ` Andi Kleen
2004-11-03 16:32               ` Brent Casavant
2004-11-03 21:00                 ` Martin J. Bligh
2004-11-08 19:58                   ` Brent Casavant
2004-11-08 20:57                     ` Martin J. Bligh
2004-11-09 19:04                     ` Hugh Dickins
2004-11-09 20:09                       ` Martin J. Bligh
2004-11-09 21:08                         ` Hugh Dickins
2004-11-09 22:07                           ` Martin J. Bligh
2004-11-10  2:41                       ` Brent Casavant
2004-11-10 14:20                         ` Hugh Dickins [this message]
2004-11-11 19:48                       ` Hugh Dickins
2004-11-11 23:10                         ` Brent Casavant
2004-11-15 22:07                         ` Brent Casavant

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=Pine.LNX.4.44.0411101406360.2806-100000@localhost.localdomain \
    --to=hugh@veritas.com \
    --cc=adam@yggdrasil.com \
    --cc=ak@suse.de \
    --cc=bcasavan@sgi.com \
    --cc=colpatch@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mbligh@aracnet.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