From: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Klaus Wacker <Klaus.Wacker-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: no-snoop flag in memory registration?
Date: Thu, 25 Oct 2012 17:49:55 +0200 [thread overview]
Message-ID: <50895FA3.1090204@mellanox.com> (raw)
In-Reply-To: <OF72E3714A.302C2D7F-ONC1257AA0.004EFF39-C1257AA0.004FEEE9-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
On 23/10/2012 16:32, Klaus Wacker wrote:
> we are implementing a Linux/RDMA solution based on Mellanox/RoCE. Our memory registration is done via "ib_get_dma_mr()". During a problem follow-up someone asked us about the "no-snoop" flag and how it is set during memory registration in Linux.
Can you describe the problem you are trying to solve and what is the
semantics you are looking for with "no snoop" -- which snooping and by
what entity.
Or.
> I digged into
> drivers/net/ethernet/mellanox/mlx4/mr.c, to find some MLX4_MPT_FLAGS_
> visible there. Nothing seems to be related to a "no-snoop" flag.
> Can anybody shed some light on this, whether we can set the so called
> "no-snoop" flag, or is that beyond the scope of Linux support.
>
> Kind regards
> Klaus Wacker
> IBM Systems &Technology Group, Systems Software Development
> SW Linux on System z Dev & Service
> Phone: +49-7031-16-3779 IBM Deutschland E-Mail: kdwacker-JZgbryFSZvw@public.gmane.orgcom
> Schoenaicher Str. 220 71032 Boeblingen Germany
> IBM Deutschland Research & Development GmbH / Vorsitzende des
> Aufsichtsrats: Martina Koederitz
> Geschäftsführung: Dirk Wittkopp
> Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart,
> HRB 243294
>
> --
> 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
--
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
prev parent reply other threads:[~2012-10-25 15:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 14:32 no-snoop flag in memory registration? Klaus Wacker
[not found] ` <OF72E3714A.302C2D7F-ONC1257AA0.004EFF39-C1257AA0.004FEEE9-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2012-10-25 15:49 ` Or Gerlitz [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=50895FA3.1090204@mellanox.com \
--to=ogerlitz-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=Klaus.Wacker-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.