mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tom Zanussi <zanussi@us.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Tom Zanussi <zanussi@us.ibm.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Greg KH <greg@kroah.com>, Andrew Morton <akpm@osdl.org>,
	Andi Kleen <ak@muc.de>, Roman Zippel <zippel@linux-m68k.org>,
	Robert Wisniewski <bob@watson.ibm.com>,
	Tim Bird <tim.bird@AM.SONY.COM>,
	karim@opersys.com
Subject: Re: [PATCH] relayfs redux, part 3
Date: Fri, 4 Feb 2005 16:00:37 -0600	[thread overview]
Message-ID: <16899.61573.300431.860574@tut.ibm.com> (raw)
In-Reply-To: <20050204211014.GA25680@infradead.org>

Christoph Hellwig writes:
 > First set of comments.  Mostly ignores the actual filesystem sematics
 > bits, that'll come next.
 > 
 > 
 > > +#
 > > +# relayfs Makefile
 > > +#
 > 
 > probably superflous comment ;-)
 > 
 > > +	mem = vmap(*page_array, *page_count, GFP_KERNEL, PAGE_KERNEL);
 > 
 > Do you really need to vmap it, and eat up vmallocspace and TLB entries?
 > Maybe some simple arithmetics on a page array could replace it?
 > 

I would really like to not vmap it, but I don't know how else to
create a large kernel virtual address space for the large buffers that
might be needed for some applications like ltt.  Maybe managing a
bunch of large kmalloc'ed buffers instead would work, but there's no
guarantee how many of those you'd be able to get at one time.  Doing
arithmetic on pages seems like it would be too much overhead for the
fast logging path, but please let me know if I'm missing something.

Thanks for all the other comments - I'll be sure to make those fixes.

Tom


  reply	other threads:[~2005-02-04 22:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-04 20:17 Tom Zanussi
2005-02-04 21:10 ` Christoph Hellwig
2005-02-04 22:00   ` Tom Zanussi [this message]
2005-02-04 21:39 ` Christoph Hellwig
2005-02-04 22:06   ` Tom Zanussi
2005-02-04 22:12 ` Andi Kleen
2005-02-04 22:22   ` Tom Zanussi
2005-02-05  6:57     ` Andi Kleen
2005-02-05  9:54 ` [PATCH] relayfs redux, part 3 II - another comment Andi Kleen

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=16899.61573.300431.860574@tut.ibm.com \
    --to=zanussi@us.ibm.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=bob@watson.ibm.com \
    --cc=greg@kroah.com \
    --cc=hch@infradead.org \
    --cc=karim@opersys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tim.bird@AM.SONY.COM \
    --cc=zippel@linux-m68k.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

all inboxes | Powered by JetHome®