From: Goldwyn Rodrigues <rgoldwyn-l3A5Bk7waGM@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH 00/11] New Caching mechanism for ib_core
Date: Wed, 9 Nov 2011 17:49:08 +0530 [thread overview]
Message-ID: <20111109121907.GA6763@shrek.cartoons> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A8237316E8DDCE-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
Thanks Sean for the review.
On Tue, Nov 08, 2011 at 11:46:50PM +0000, Hefty, Sean wrote:
> > The main motivations are:
> >
> > 1. Greater degree of control by individual drivers. Drivers have a
> > choice to use it or not.
>
> I believe that some callers need to know that specific query calls will not sleep. That capability should either be required or exposed through the API.
The new cache access functions do not sleep. This is the primary
objective of the exercise. See motviation 2 :)
Exceptions are the init functions which may sleep because of kzalloc().
Did you want me to mention this specifically in the comments?
>
> > 2. The library functions do not sleep, and can be called from any context.
> >
> > In the bargain we lose the lmc cache. However, if we move it to the device
> > structure like the pkey_tbl_len, it can be accessed directly (TODO).
> > Let me know what you think about it.
>
> The LMC cache is accessed by the MAD layer. I know that MADs aren't considered a performance path, but we don't want to query the device for every MAD.
>
I understand. I will try to incorporate the lmc cache in the device
structure while I wait for the rest of the comments.
Regards,
--
Goldwyn
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-11-09 12:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 8:47 [PATCH 00/11] New Caching mechanism for ib_core Goldwyn Rodrigues
[not found] ` <20111107084747.GA11297-DN/iB9hNKqpUanf73oPxOg@public.gmane.org>
2011-11-08 23:46 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A8237316E8DDCE-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-11-09 12:19 ` Goldwyn Rodrigues [this message]
[not found] ` <20111109121907.GA6763-DN/iB9hNKqpUanf73oPxOg@public.gmane.org>
2011-11-09 15:12 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A8237316E8DE44-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-11-10 4:20 ` Goldwyn Rodrigues
[not found] ` <20111110042029.GA7713-DN/iB9hNKqpUanf73oPxOg@public.gmane.org>
2011-11-10 7:03 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A8237316E95317-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-11-11 4:15 ` Goldwyn Rodrigues
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=20111109121907.GA6763@shrek.cartoons \
--to=rgoldwyn-l3a5bk7wagm@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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