All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@minantech.com>
To: "Michael S. Tsirkin" <mst@mellanox.co.il>
Cc: Hugh Dickins <hugh@veritas.com>,
	William Irwin <wli@holomorphy.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Petr Vandrovec <vandrove@vc.cvut.cz>,
	Nick Piggin <nickpiggin@yahoo.com.au>,
	Badari Pulavarty <pbadari@us.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	openib-general@openib.org
Subject: Re: madvise MADV_DONTFORK/MADV_DOFORK
Date: Tue, 14 Feb 2006 08:51:45 +0200	[thread overview]
Message-ID: <20060214065145.GE24524@minantech.com> (raw)
In-Reply-To: <20060213190206.GC12458@mellanox.co.il>

On Mon, Feb 13, 2006 at 09:02:06PM +0200, Michael S. Tsirkin wrote:
> Quoting r. Hugh Dickins <hugh@veritas.com>:
> > > Add madvise options to control whether memory range is inherited across fork.
> > > Useful e.g. for when hardware is doing DMA from/into these pages.
> > > 
> > > Signed-off-by: Michael S. Tsirkin <mst@mellanox.co.il>
> > 
> > Looks good to me, Michael (but Gleb's eye has always proved better than
> > mine).  Just a couple of adjustments I'd ask before you send to Andrew: 
> 
> Gleb has acked this to me in a private mail.
> Right, Gleb?
> 
Sory to be late :)

Yes the patch is looking good.

Acked-by: Gleb Natapov <glebn@voltaire.com>

--
			Gleb.

  reply	other threads:[~2006-02-14  6:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-13 15:41 madvise MADV_DONTFORK/MADV_DOFORK Michael S. Tsirkin
2006-02-13 18:23 ` Hugh Dickins
2006-02-13 19:02   ` Michael S. Tsirkin
2006-02-14  6:51     ` Gleb Natapov [this message]
2006-02-13 19:04 ` [openib-general] " Roland Dreier
2006-02-13 19:05 ` Linus Torvalds
2006-02-13 19:16   ` [openib-general] " Roland Dreier
2006-02-13 19:34     ` Linus Torvalds
2006-02-13 19:50       ` Hugh Dickins
2006-02-13 21:09         ` Michael S. Tsirkin
2006-02-13 21:57           ` Hugh Dickins
2006-02-13 22:09             ` Michael S. Tsirkin
2006-02-13 22:54               ` Hugh Dickins
2006-02-13 23:01                 ` [PATCH] " Michael S. Tsirkin
2006-02-13 23:44                   ` Hugh Dickins
2006-02-13 22:27             ` [openib-general] " Linus Torvalds
2006-02-13 22:55               ` Michael S. Tsirkin
2006-02-13 23:01                 ` Hugh Dickins
2006-02-13 23:35                   ` [PATCH] " Michael S. Tsirkin
2006-02-15  4:31                     ` Nick Piggin
2006-02-15  6:09                       ` Roland Dreier
2006-02-15  6:16                         ` Andrew Morton
2006-02-15  6:34                           ` [PATCH] Fix up MADV_DONTFORK/MADV_DOFORK definitions Roland Dreier
2006-02-15  6:48                             ` Gleb Natapov
2006-02-15  7:06                               ` Nick Piggin
2006-02-15  7:31                             ` Bernd Eckenfels
2006-02-15  8:18                             ` Michael S. Tsirkin
2006-02-15  8:13                         ` [PATCH] madvise MADV_DONTFORK/MADV_DOFORK Michael S. Tsirkin
2006-02-13 20:05       ` Michael S. Tsirkin
2006-02-13 19:20   ` Michael S. Tsirkin

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=20060214065145.GE24524@minantech.com \
    --to=gleb@minantech.com \
    --cc=benh@kernel.crashing.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@mellanox.co.il \
    --cc=nickpiggin@yahoo.com.au \
    --cc=openib-general@openib.org \
    --cc=pbadari@us.ibm.com \
    --cc=vandrove@vc.cvut.cz \
    --cc=wli@holomorphy.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.