linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Jes Sorensen <jes@sunsite.dk>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	jgarzik@mandrakesoft.com (Jeff Garzik),
	bcrl@redhat.com (Ben LaHaise),
	hiren_mehta@agilent.com ("MEHTA,HIREN (A-SanJose,ex1)"),
	linux-kernel@vger.kernel.org ('linux-kernel@vger.kernel.org')
Subject: Re: (reposting) how to get DMA'able memory within 4GB on 64-bit m
Date: Wed, 11 Jul 2001 16:07:01 -0700 (PDT)	[thread overview]
Message-ID: <15180.56341.731014.82811@pizda.ninka.net> (raw)
In-Reply-To: <d3y9pv8ee5.fsf@lxplus015.cern.ch>
In-Reply-To: <3B46FDF1.A38E5BB6@mandrakesoft.com> <E15Ir5R-0005lR-00@the-village.bc.nu> <15175.2003.773317.101601@pizda.ninka.net> <d3y9pv8ee5.fsf@lxplus015.cern.ch>


Jes Sorensen writes:
 > The overhead is going be negligeble, the overhead of highmem itself is
 > much worse.

Once Jens's block layer stuff goes in, a lot of that overhead simply
disappears since the page cache need not bounce buffers.  The
networking can already technically cope with this too.

 > Not to mention that today some dma_addr_t's might not be
 > packed properly in data structure hence they ending up taking 8 bytes
 > anyway.

Not on x86 which is the current main benefactor of highmem.

Later,
David S. Miller
davem@redhat.com

      parent reply	other threads:[~2001-07-11 23:07 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-28 16:20 (reposting) how to get DMA'able memory within 4GB on 64-bit m achi ne MEHTA,HIREN (A-SanJose,ex1)
2001-06-28 19:41 ` Jes Sorensen
2001-06-28 21:45 ` David S. Miller
2001-06-28 22:01 ` David S. Miller
2001-06-28 22:20   ` Jes Sorensen
2001-06-28 22:28     ` Alan Cox
2001-07-02  8:09       ` Jens Axboe
2001-06-28 22:24   ` Ben LaHaise
2001-07-02  8:09     ` Jens Axboe
2001-06-28 22:27   ` David S. Miller
2001-06-28 22:29   ` David S. Miller
2001-06-28 22:31     ` Ben LaHaise
2001-06-28 22:40       ` (reposting) how to get DMA'able memory within 4GB on 64-bit m Alan Cox
2001-06-28 22:38     ` (reposting) how to get DMA'able memory within 4GB on 64-bit m achi ne David S. Miller
2001-06-28 22:45       ` Ben LaHaise
2001-06-28 22:48       ` David S. Miller
2001-06-28 22:48       ` (reposting) how to get DMA'able memory within 4GB on 64-bit m Alan Cox
2001-06-28 22:55       ` (reposting) how to get DMA'able memory within 4GB on 64-bit m achi ne Jes Sorensen
2001-06-29  9:16       ` David S. Miller
2001-06-29  9:56         ` Alan Cox
2001-06-29 20:37         ` David S. Miller
2001-07-05 21:06           ` Jes Sorensen
2001-07-05 23:47           ` David S. Miller
2001-07-05 23:50             ` Ben LaHaise
2001-07-06 13:31             ` Jes Sorensen
2001-07-06 23:46             ` David S. Miller
2001-07-07  3:58               ` Ben LaHaise
2001-07-07  5:35               ` David S. Miller
2001-07-07 12:06                 ` (reposting) how to get DMA'able memory within 4GB on 64-bit m Alan Cox
2001-07-07 12:17                   ` Jeff Garzik
2001-07-07 12:21                     ` Alan Cox
2001-07-07 13:00                     ` David S. Miller
2001-07-11 19:16                       ` Jes Sorensen
2001-07-11 21:54                         ` Chris Wedgwood
2001-07-11 23:17                         ` David S. Miller
2001-07-11 23:07                       ` David S. Miller [this message]

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=15180.56341.731014.82811@pizda.ninka.net \
    --to=davem@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bcrl@redhat.com \
    --cc=hiren_mehta@agilent.com \
    --cc=jes@sunsite.dk \
    --cc=jgarzik@mandrakesoft.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;
as well as URLs for NNTP newsgroup(s).