linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Christoph Raisch <RAISCH@de.ibm.com>
Cc: Thomas Q Klein <tklein@de.ibm.com>,
	"Jenkins, Clive" <Clive.Jenkins@xerox.com>,
	netdev <netdev@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-ppc <linuxppc-dev@ozlabs.org>,
	Marcus Eder <meder@de.ibm.com>
Subject: RE: [PATCH 4/6] ehea: header files
Date: Wed, 16 Aug 2006 10:58:35 +1000	[thread overview]
Message-ID: <1155689915.26911.12.camel@localhost.localdomain> (raw)
In-Reply-To: <OF8C6BA147.30EE53F8-ONC12571CB.003C7748-C12571CB.003CBAA4@de.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]

On Tue, 2006-08-15 at 13:07 +0200, Christoph Raisch wrote:
> 
> "Jenkins, Clive" wrote on 15.08.2006 12:53:05:
> 
> > > > You mean the eHEA has its own concept of page size? Separate from
> > the
> > > > page size used by the MMU?
> > > >
> > >
> > > yes, the eHEA currently supports only 4K pages for queues
> >
> > In that case, I suggest use the kernel's page size, but add a
> > compile-time
> > check, and quit with an error message if driver does not support it.
> 
> eHEA does support other page sizes than 4k, but the HW interface expects to
> see 4k pages
> The adaption is done in the device driver, therefore we have a seperate 4k
> define.

Fair enough. You seem to only use it in drivers/net/ehea/ehea_qmr.c, if
so put the definition in there, that way someone is less likely to use
the EHEA_PAGESIZE definition where they really need PAGE_SIZE.

cheers

-- 
Michael Ellerman
IBM OzLabs

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

  parent reply	other threads:[~2006-08-16  0:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-09  8:39 [PATCH 4/6] ehea: header files Jan-Bernd Themann
2006-08-09 13:17 ` Arnd Bergmann
2006-08-10  6:22 ` Michael Ellerman
2006-08-14 12:53   ` Jan-Bernd Themann
2006-08-15  0:08     ` Michael Ellerman
2006-08-15  9:44       ` Jan-Bernd Themann
2006-08-15 10:53         ` Jenkins, Clive
2006-08-15 11:07           ` Christoph Raisch
2006-08-15 11:09             ` edlk4.0 ppc_85xx gdb problems emre kara
2006-08-15 11:46               ` Jenkins, Clive
2006-08-16  0:58             ` Michael Ellerman [this message]
2006-08-11 21:40 ` [PATCH 4/6] ehea: header files Anton Blanchard
2006-08-14  3:20   ` Michael Ellerman
2006-08-14  6:19     ` Jan-Bernd Themann
2006-08-11 22:07 ` Anton Blanchard
2006-08-12 16:40   ` Thomas Klein

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=1155689915.26911.12.camel@localhost.localdomain \
    --to=michael@ellerman.id.au \
    --cc=Clive.Jenkins@xerox.com \
    --cc=RAISCH@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=meder@de.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=tklein@de.ibm.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 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).