From: Peter Zaitsev <pz@spylog.ru>
To: Brian Gerst <bgerst@didntduck.org>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re[2]: 3.5G user space speed
Date: Wed, 16 Jan 2002 00:28:57 +0300 [thread overview]
Message-ID: <15850171252.20020116002857@spylog.ru> (raw)
In-Reply-To: <3C4499A3.781E5A85@didntduck.org>
In-Reply-To: <16247691406.20020115234737@spylog.ru> <3C4499A3.781E5A85@didntduck.org>
Hello Brian,
Wednesday, January 16, 2002, 12:05:39 AM, you wrote:
Well. May be you can tell about the numbers a bit ? I can chose 3.0G
for user instead of 3.5G for user with not really huge loss, but I'd
like to know how much it will increase speed and in which cases, also
about standard 2/2 mode.
>>
>> 2.4.xaa Series as well as SuSE kernels have 3.5G userspace option,
>> which seems to be quite useful, therefore I see it's not included
>> is stock kernel for some reasons. Also I've heard this
>> configuration may have some performance problems.
>>
>> Can anyone comment on this topic ?
>>
>> I need large amount of address space for my application but I also
>> need to get as much I/O performance as it's possible, so I can switch
>> to 3.0/1.0 memory distribution if it will benefit here.
BG> You can't have it both ways with the x86 (speed vs. large userspace).
BG> Kernel 2.5 may help a bit here because changes were made to allow DMA
BG> from all memory (subject to card limitations), lessening the burden for
BG> direct-mapped memory. Otherwise you'll need to move to a 64-bit arch.
--
Best regards,
Peter mailto:pz@spylog.ru
next prev parent reply other threads:[~2002-01-15 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 20:47 Peter Zaitsev
2002-01-15 21:05 ` Brian Gerst
2002-01-15 21:28 ` Peter Zaitsev [this message]
2002-01-15 21:41 ` Brian Gerst
2002-01-15 21:49 ` Re[2]: " Peter Zaitsev
2002-01-15 22:09 ` H. Peter Anvin
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=15850171252.20020116002857@spylog.ru \
--to=pz@spylog.ru \
--cc=bgerst@didntduck.org \
--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
all inboxes | Powered by JetHome®