From: David Gibson <david@gibson.dropbear.id.au>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: ccan@lists.ozlabs.org
Subject: Re: [PATCH 2/2] mem: Add memswap() function
Date: Wed, 9 Sep 2015 17:37:59 +1000 [thread overview]
Message-ID: <20150909073759.GE17641@voom.redhat.com> (raw)
In-Reply-To: <87k2s04uz5.fsf@rustcorp.com.au>
[-- Attachment #1.1: Type: text/plain, Size: 732 bytes --]
On Wed, Sep 09, 2015 at 04:08:38AM +0930, Paul 'Rusty' Russell wrote:
> David Gibson <david@gibson.dropbear.id.au> writes:
> > Add a memswap() function to the mem module, which exchanges two (equal
> > sized, non-overlapping) memory regions.
>
> Nice!
>
> I wonder about a #if CCAN_MEM_DEBUG'd test which assert() tests for
> no overlap.
>
> Though maybe it's cheap enough that a simple assert() is always OK?
Good idea. And actually.. an exposed function to tell if memory
ranges overlap might be nice too, why not.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
ccan mailing list
ccan@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/ccan
prev parent reply other threads:[~2015-09-09 7:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-05 4:44 [PATCH 0/2] Small extensions to the mem module David Gibson
2015-09-05 4:44 ` [PATCH 1/2] mem: Remove array_size dependency David Gibson
2015-09-05 4:44 ` [PATCH 2/2] mem: Add memswap() function David Gibson
2015-09-08 18:38 ` Rusty Russell
2015-09-09 7:37 ` David Gibson [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=20150909073759.GE17641@voom.redhat.com \
--to=david@gibson.dropbear.id.au \
--cc=ccan@lists.ozlabs.org \
--cc=rusty@rustcorp.com.au \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).