linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dave.martin@linaro.org (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: Discontiguous memory and cacheflush
Date: Thu, 16 Aug 2012 10:43:18 +0100	[thread overview]
Message-ID: <20120816094318.GB2101@linaro.org> (raw)
In-Reply-To: <20120816091953.GL18957@n2100.arm.linux.org.uk>

On Thu, Aug 16, 2012 at 10:19:53AM +0100, Russell King - ARM Linux wrote:
> On Thu, Aug 16, 2012 at 09:27:26AM +0100, Dave Martin wrote:
> > Could we use the currently must-be-zero flags parameter to add new
> > functionality to this syscall, or are there legacy uses of that
> > parameter (or history of userspace not bothering to zero it?)
> > 
> > For example, we could have something like
> > 
> > do_cache_op(struct iovec *iov, int iovcnt, CF_IOVEC)
> > 
> > to flush a discontiguous set of ranges described by an iovec (though we
> > can of course also describe the ranges in other ways)
> 
> Why overload an existing syscall with multiple different argument types
> rather than having a new syscall with a sane API?

Sure, if it's OK to add a new system call, that would be a cleaner
approach.

Cheers
---Dave

  reply	other threads:[~2012-08-16  9:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <447177957.1189939.1344577602635.JavaMail.root@mozilla.com>
2012-08-10  5:52 ` Discontiguous memory and cacheflush Martin Rosenberg
2012-08-13 14:42   ` Jonathan Austin
2012-08-13 16:00     ` Russell King - ARM Linux
2012-08-15 22:08       ` Martin Rosenberg
2012-08-16  8:27         ` Dave Martin
2012-08-16  9:19           ` Russell King - ARM Linux
2012-08-16  9:43             ` Dave Martin [this message]
2012-08-17 15:53         ` Jonathan Austin
2012-08-17 21:03           ` Russell King - ARM Linux

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=20120816094318.GB2101@linaro.org \
    --to=dave.martin@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).