linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: Shuvabrata Ganguly <sganguly@cse.iitkgp.ernet.in>
Cc: "Stephen C. Tweedie" <sct@redhat.com>, linux-mm@kvack.org
Subject: Re: Question about pte_alloc()
Date: Thu, 16 Nov 2000 15:37:28 +0100	[thread overview]
Message-ID: <20001116153728.E703@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <3A144453.D0724CC1@cse.iitkgp.ernet.in>; from sganguly@cse.iitkgp.ernet.in on Thu, Nov 16, 2000 at 03:32:19PM -0500

On Thu, Nov 16, 2000 at 03:32:19PM -0500, Shuvabrata Ganguly wrote:
> i know that. but i dont want to wire the pages. i want the driver to allocate
> pages, fill them up with data and then transfer them to the user, which would
> enable the kernel to swap them  but then i cant touch page tables at interrupt
> time.

Why don't you use an allocator/deliver thread, a ringbuffer and
throw away the overflowing packets, while signalling the sender,
that you are satiated for the moment? The overflowing packets
will be resent later anyway.

If you receive sth., you just put it into the deliver queue and
wake the thread to deliver (==map) it.

BTW: Zero copy might become pointless if you use threads or play
   VM-Tricks.

BTW2: Are you aware of U-Net and VIA?

Regards

Ingo Oeser
-- 
To the systems programmer, users and applications
serve only to provide a test load.
<esc>:x
--
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.eu.org/Linux-MM/

  reply	other threads:[~2000-11-16 14:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-15  7:07 Shuvabrata Ganguly
2000-11-14 20:51 ` Kanoj Sarcar
2000-11-15 10:56 ` Stephen C. Tweedie
2000-11-16  0:04   ` Shuvabrata Ganguly
2000-11-15 15:47     ` Stephen C. Tweedie
2000-11-16 20:32       ` Shuvabrata Ganguly
2000-11-16 14:37         ` Ingo Oeser [this message]
2000-11-15 15:20 Mark_H_Johnson
2000-11-15 15:34 ` Stephen C. Tweedie

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=20001116153728.E703@nightmaster.csn.tu-chemnitz.de \
    --to=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=linux-mm@kvack.org \
    --cc=sct@redhat.com \
    --cc=sganguly@cse.iitkgp.ernet.in \
    /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