From: Christoph Hellwig <hch@infradead.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC 0/4] Add SN2 Special Memory driver.
Date: Fri, 10 Sep 2004 08:32:06 +0000 [thread overview]
Message-ID: <20040910093206.A22171@infradead.org> (raw)
In-Reply-To: <20040909163638.GA23178@lnx-holt.americas.sgi.com>
On Fri, Sep 10, 2004 at 03:31:13AM -0500, Robin Holt wrote:
> On Fri, Sep 10, 2004 at 08:33:57AM +0100, Christoph Hellwig wrote:
> > On Thu, Sep 09, 2004 at 12:59:37PM -0500, Robin Holt wrote:
> > > I am not sure how to read this. The fetchop function is a feature specifically
> > > in the SN2 memory controller. Are you saying we should have a driver that
> > > provides fetchops for all ia64? That seems wrong since it is a hardware feature.
> > >
> > > If, on the other hand, you are saying that the uncached and cached drivers
> > > should be available for all ia64 and the fetchop only if you are on sn2, I
> > > can understand that. That actually seems rather reasonable.
> >
> > Yes, that's what I meant. Even if it's mostly useful for SGI's userland
> > it's implementation shouldn't depend on a SN2 kernel if it doesn't use any
> > SN2-specific functionality.
>
> Do any other processors have the write combining features of the ia64? Is this
> type of memory useable by any other processor? If not, does this driver belong
> in the arch/ia64/kernel directory?
Umm, yes I guess it'll be ia64-specific at least as a start, I just wanted to
avoid having it SN2-specific.
next prev parent reply other threads:[~2004-09-10 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 16:36 [RFC 0/4] Add SN2 Special Memory driver Robin Holt
2004-09-09 17:21 ` Christoph Hellwig
2004-09-09 17:59 ` Robin Holt
2004-09-10 7:33 ` Christoph Hellwig
2004-09-10 8:31 ` Robin Holt
2004-09-10 8:32 ` Christoph Hellwig [this message]
2004-09-10 15:34 ` Jesse Barnes
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=20040910093206.A22171@infradead.org \
--to=hch@infradead.org \
--cc=linux-ia64@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