| To: | Ashutosh Rajekar <arajekar@xxxxxxxxx> |
|---|---|
| Subject: | Re: [Myricom help #36078] application sleeps indefinitely trying to read gm_dma_malloc'ed buffer through O_DIRECT |
| From: | Myricom Technical Support <help@xxxxxxxx> |
| Date: | Tue, 30 Aug 2005 15:15:19 -0400 |
| Cc: | linux-xfs@xxxxxxxxxxx, ocrete@xxxxxxxxx, Myricom Technical Support <help@xxxxxxxx> |
| In-reply-to: | <44876.192.168.1.140.1125426070.squirrel@ftp.max-t.com> |
| Organization: | Myricom, Inc. |
| References: | <44876.192.168.1.140.1125426070.squirrel@ftp.max-t.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla Thunderbird 1.0.2 (X11/20050317) |
Hi, Ashutosh, Disabling the O_DIRECT flag makes things work fine. Using standard memory allocated (i.e. memory not registered with GM using gm_dma_malloc()) using a malloc() or a posix_memalign() makes sure it works fine too. Yes, this is a fundamental problem of conflictual use between O_DIRECT and memory registration in GM. (We are surprised to hear that this ever worked with some Linux kernels.) I have forwarded your question to our GM software developers, and they are pondering ways of allocating the initial memory differently that may allow this to work. Susan -- Susan Blackford Member of Technical Staff Myricom Inc. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: application sleeps indefinitely trying to read gm_dma_malloc'ed buffer through O_DIRECT, Christoph Hellwig |
|---|---|
| Next by Date: | Re: Will we ever see XFS supported in Red Hat Enterprise Linux?, Eric Sandeen |
| Previous by Thread: | Re: application sleeps indefinitely trying to read gm_dma_malloc'ed buffer through O_DIRECT, Christoph Hellwig |
| Next by Thread: | Re: [Myricom help #36078] application sleeps indefinitely trying to read gm_dma_malloc'ed buffer through O_DIRECT]], Myricom Technical Support |
| Indexes: | [Date] [Thread] [Top] [All Lists] |