public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	iscsitarget-devel@lists.sourceforge.net,
	linux-scsi@vger.kernel.org
Subject: Re: [ANNOUNCE] iSCSI enterprise target software
Date: Tue, 01 Mar 2005 21:38:34 +0100	[thread overview]
Message-ID: <m1d5ujp0dx.fsf@muc.de> (raw)
In-Reply-To: <1109702227.6293.137.camel@laptopd505.fenrus.org> (Arjan van de Ven's message of "Tue, 01 Mar 2005 19:37:07 +0100")

Arjan van de Ven <arjan@infradead.org> writes:
>
> You want to *use* the kernel pagecache as much as you can. You do so by
> using mmap and such, and msync to force content to disk. That uses the

Last time I checked you couldn't mmap block devices. Has this changed
now?  Could be a problem for an iSCSI target.

I remember there used to be a hack in 2.2 to map them to a pseudo fs
to allow mmaping, but that's not very nice and would require
another step by the administrator.

Also using mmap would imply the server only works on 64bit systems,
and may even there have uncomfortable limits. One issue is that
the kernel currently doesn't garbage collect page tables, so 
e.g. when you map a 10TB volume this way and the user accesses
it randomly you will eventually have quite a lot of page tables
filling up your RAM. And those will not go away.

My overall feeling is that mmap is not a good idea for this.

-Andi

  parent reply	other threads:[~2005-03-01 20:38 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-01  7:19 [ANNOUNCE] iSCSI enterprise target software FUJITA Tomonori
2005-03-01  8:40 ` Arjan van de Ven
2005-03-01  9:35   ` FUJITA Tomonori
2005-03-01  9:46     ` Arjan van de Ven
2005-03-01 10:22       ` [Iscsitarget-devel] " FUJITA Tomonori
2005-03-01 10:33         ` Arjan van de Ven
2005-03-01 10:46           ` Arjan van de Ven
2005-03-01 11:23             ` FUJITA Tomonori
2005-03-01 10:48           ` Libor Vanek
2005-03-01 10:51             ` Arjan van de Ven
2005-03-01 18:24     ` Bryan Henderson
2005-03-01 18:37       ` Arjan van de Ven
2005-03-01 18:48         ` Ming Zhang
2005-03-01 19:01           ` Jeff Garzik
2005-03-01 19:14             ` Ming Zhang
2005-03-01 21:04           ` Bryan Henderson
2005-03-01 21:15             ` Ming Zhang
2005-03-02 18:20               ` Bryan Henderson
2005-03-02 19:34                 ` Ming Zhang
2005-03-01 21:16             ` Arjan van de Ven
2005-03-02 18:27               ` Bryan Henderson
2005-03-02  3:30             ` FUJITA Tomonori
2005-03-01 20:38         ` Andi Kleen [this message]
2005-03-01 20:49           ` Ming Zhang
2005-03-01 22:19           ` Christoph Hellwig
2005-03-01 20:53         ` Bryan Henderson
2005-03-01 20:58           ` Arjan van de Ven
2005-03-02 10:47           ` Vladislav Bolkhovitin
2005-03-02 18:39             ` Bryan Henderson
2005-03-02  5:04     ` [Iscsitarget-devel] " FUJITA Tomonori
2005-03-02  5:21       ` Dmitry Yusupov

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=m1d5ujp0dx.fsf@muc.de \
    --to=ak@muc.de \
    --cc=arjan@infradead.org \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=iscsitarget-devel@lists.sourceforge.net \
    --cc=linux-scsi@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